Re: oops in ioapic_write_entry

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Eric W. Biederman
Date: Wednesday, August 4, 2010 - 5:12 am

Yinghai Lu <yinghai@kernel.org> writes:


This looks roughly like the right approach.
However I don't see what would force the ioapic entries before
the intsrc entries in the table.  Especially when the assumption
is we are dealing with a buggy bios.


If we can make the algorithm two pass picking up the ioapic
entries first this should be fine.


In practice your test of looking at mp_bus_not_pci is essentially what
we do.  I wonder if it could be made to be a test of polarity and edge
mismatch instead.

Also if we are ditching a non-duplicate intsrc we want to print a message
so there is a chance of debugging things if our heuristic for fixing
up broken BIOS's goes wrong, on some common configuration.


That should be.


Eric
--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
oops in ioapic_write_entry, Dave Airlie, (Sun Aug 1, 10:28 pm)
Re: oops in ioapic_write_entry, Yinghai Lu, (Sun Aug 1, 11:49 pm)
Re: oops in ioapic_write_entry, Dave Airlie, (Mon Aug 2, 4:17 pm)
Re: oops in ioapic_write_entry, Yinghai Lu, (Mon Aug 2, 6:32 pm)
Re: oops in ioapic_write_entry, Yinghai Lu, (Mon Aug 2, 6:34 pm)
Re: oops in ioapic_write_entry, Eric W. Biederman, (Mon Aug 2, 8:13 pm)
Re: oops in ioapic_write_entry, Eric W. Biederman, (Mon Aug 2, 8:26 pm)
Re: oops in ioapic_write_entry, Eric W. Biederman, (Mon Aug 2, 11:00 pm)
Re: oops in ioapic_write_entry, Yinghai Lu, (Tue Aug 3, 12:19 am)
Re: oops in ioapic_write_entry, Eric W. Biederman, (Tue Aug 3, 1:00 am)
Re: oops in ioapic_write_entry, Yinghai Lu, (Tue Aug 3, 1:00 am)
Re: oops in ioapic_write_entry, Yinghai Lu, (Tue Aug 3, 1:04 am)
Re: oops in ioapic_write_entry, Eric W. Biederman, (Tue Aug 3, 1:27 am)
Re: oops in ioapic_write_entry, Eric W. Biederman, (Tue Aug 3, 1:56 am)
Re: oops in ioapic_write_entry, Yinghai Lu, (Tue Aug 3, 2:01 am)
Re: oops in ioapic_write_entry, Eric W. Biederman, (Tue Aug 3, 2:15 am)
Re: oops in ioapic_write_entry, Yinghai Lu, (Tue Aug 3, 2:36 am)
Re: oops in ioapic_write_entry, Eric W. Biederman, (Tue Aug 3, 4:08 am)
Re: oops in ioapic_write_entry, Yinghai Lu, (Tue Aug 3, 12:45 pm)
Re: oops in ioapic_write_entry, Yinghai Lu, (Tue Aug 3, 1:02 pm)
Re: oops in ioapic_write_entry, Eric W. Biederman, (Tue Aug 3, 2:38 pm)
Re: oops in ioapic_write_entry, Dave Airlie, (Tue Aug 3, 4:12 pm)
Re: oops in ioapic_write_entry, Yinghai Lu, (Tue Aug 3, 5:00 pm)
Re: oops in ioapic_write_entry, Eric W. Biederman, (Tue Aug 3, 6:19 pm)
Re: oops in ioapic_write_entry, Ingo Molnar, (Wed Aug 4, 12:33 am)
Re: oops in ioapic_write_entry, Yinghai Lu, (Wed Aug 4, 1:59 am)
Re: oops in ioapic_write_entry, Ingo Molnar, (Wed Aug 4, 2:26 am)
Re: oops in ioapic_write_entry, Eric W. Biederman, (Wed Aug 4, 5:12 am)
Re: oops in ioapic_write_entry, Yinghai Lu, (Wed Aug 4, 12:22 pm)
Re: oops in ioapic_write_entry, Eric W. Biederman, (Wed Aug 4, 1:34 pm)
Re: oops in ioapic_write_entry, Yinghai Lu, (Wed Aug 4, 3:06 pm)