On Wed, Aug 08, 2007 at 01:42:43PM +0200, Jarek Poplawski wrote: ... > So, it looks like x86_64 io_apic's IPI code was unused too long... To be fair it's x86_64 lapic's IPI code. Jarek P. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- References:
- Re: 2.6.20->2.6.21 - networking dies after random time
- From: Jarek Poplawski <[email protected]>
- Re: 2.6.20->2.6.21 - networking dies after random time
- From: "Marcin Ślusarz" <[email protected]>
- Re: 2.6.20->2.6.21 - networking dies after random time
- From: Ingo Molnar <[email protected]>
- Re: 2.6.20->2.6.21 - networking dies after random time
- From: "Marcin Ślusarz" <[email protected]>
- Re: 2.6.20->2.6.21 - networking dies after random time
- From: Jarek Poplawski <[email protected]>
- Re: 2.6.20->2.6.21 - networking dies after random time
- From: Jarek Poplawski <[email protected]>
- Re: 2.6.20->2.6.21 - networking dies after random time
- From: Jarek Poplawski <[email protected]>
- Re: 2.6.20->2.6.21 - networking dies after random time
- From: "Marcin Ślusarz" <[email protected]>
- Re: 2.6.20->2.6.21 - networking dies after random time
- From: Jarek Poplawski <[email protected]>
- Re: 2.6.20->2.6.21 - networking dies after random time
- Prev by Date: Re: [PATCH 18/25] [PATCH] turn priviled operations into macros in entry.S
- Next by Date: Re: allow non root users to set io priority "idle" ?
- Previous by thread: Re: 2.6.20->2.6.21 - networking dies after random time
- Next by thread: [patch (testing)] Re: 2.6.20->2.6.21 - networking dies after random time
- Index(es):
 |