Found 13 matching messages (0.113 seconds). Page 1 of 1.
... tell went blindly into the x86 tree without being shared on ... interference: you interrupt a processor by moving a designated memory area ... was too much risk of breakage to take it. How come ... an identical patch with different authorship could go in to your ...
linux-kernel - James Bottomley - Apr 27 2008 - 16:51
... can tell went blindly into the x86 tree without being > > shared on ... if the bios was broken in how it set up MTRR' ... and notice, not the actual patch. > When you're mapping device ... breakage was exceptional ... I expect other problems just to result in ...
linux-kernel - James Bottomley - Apr 27 2008 - 19:03
...
linux-kernel - David Miller - Apr 27 2008 - 19:00
...
linux-kernel - Arjan van de Ven - Apr 27 2008 - 19:07
... James.Bottomley@HansenPartnership.com> wrote: > This patch: > > commit 6371b495991debfd1417b17c2bc4f7d7bae05739 > Author: Ingo Molnar < ... can tell went blindly into the x86 tree without being > shared on ... if the bios was broken in how it set up MTRR's ...
linux-kernel - Arjan van de Ven - Apr 27 2008 - 18:58
... add that the intel SAPIC functions > in roughly the same manner, so this ... only mention of SAPIC in the x86 tree appear to be naming of fields in ACPI tables. -hpa -- To unsubscribe ... the line "unsubscribe linux-kernel" in the body of a message to ...
linux-kernel - H. Peter Anvin - Apr 27 2008 - 18:00
... add that the intel SAPIC functions > > in roughly the same manner, so this ... The only > mention of SAPIC in the x86 tree appear to be naming of fields in ACPI > tables. Yes, that's the ... send the line "unsubscribe linux-kernel" in the body of a message ...
linux-kernel - James Bottomley - Apr 27 2008 - 18:10
... add that the intel SAPIC functions >>> in roughly the same manner, so this ... The only >> mention of SAPIC in the x86 tree appear to be naming of fields in ACPI >> tables. > > Yes, that's ... the line "unsubscribe linux-kernel" in the body of a message ...
linux-kernel - H. Peter Anvin - Apr 27 2008 - 18:13
... that the intel SAPIC functions > >>> in roughly the same manner, so ... only > >> mention of SAPIC in the x86 tree appear to be naming of fields in ACPI > >> tables. > > > > Yes, that's ... the line "unsubscribe linux-kernel" in the body of a message ...
linux-kernel - James Bottomley - Apr 27 2008 - 18:18
... mailboxes, uncached does mean less > performant. The voyager breakage was exceptional ... I expect other > problems just to result in a loss of performance that caching gave by > improving the bursting. If we're lucky, the ...
linux-kernel - Arjan van de Ven - Apr 27 2008 - 19:11
... club, Ingo is upsetting a lot of people lately. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please ...
linux-kernel - David Miller - Apr 27 2008 - 16:53
... >> cacheable. I would be very interested in the details, so if you could >> ... use of cacheline-related bus cycles is generated by the LAPIC and doesn't affect the ... list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@ ...
linux-kernel - H. Peter Anvin - Apr 27 2008 - 18:31
... is the lack of review and notice, not the actual > patch. [...] > I wouldn't have picked ... I'd have asked for ... since there really is only one plausible answer (*especially* in the light of the precedents set by other architectures.) Ingo's ...
linux-kernel - H. Peter Anvin - Apr 27 2008 - 19:17