From: "H. Peter Anvin" <hpa@zytor.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Breakage caused by unreviewed patch in x86 tree
Date: Sun, 27 Apr 2008 15:13:52 -0700 [thread overview]
Message-ID: <4814FAA0.8060705@zytor.com> (raw)
In-Reply-To: <1209334212.3801.70.camel@localhost.localdomain>
James Bottomley wrote:
> On Sun, 2008-04-27 at 15:00 -0700, H. Peter Anvin wrote:
>> James Bottomley wrote:
>>> I might add that the intel SAPIC functions
>>> in roughly the same manner, so this might break more than just voyager.
>> Are you referring to the IA64 SAPIC here, or something else? The only
>> mention of SAPIC in the x86 tree appear to be naming of fields in ACPI
>> tables.
>
> Yes, that's the one ... but I believe a class of the xAPICs also used a
> similar principle.
I certainly have never seen a system on which the APIC has been mapped
cacheable. I would be very interested in the details, so if you could
elaborate that would be extremely useful.
-hpa
next prev parent reply other threads:[~2008-04-27 22:14 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-27 20:51 Breakage caused by unreviewed patch in x86 tree James Bottomley
2008-04-27 20:53 ` David Miller
2008-04-27 21:48 ` [patch] x86, voyager: fix ioremap_nocache() Ingo Molnar
2008-04-27 22:05 ` James Bottomley
2008-04-27 22:36 ` Willy Tarreau
2008-04-27 22:41 ` Ingo Molnar
2008-04-27 23:18 ` Ingo Molnar
2008-04-27 23:31 ` David Miller
2008-04-28 0:31 ` Rik van Riel
2008-04-28 0:45 ` Al Viro
2008-04-28 0:52 ` H. Peter Anvin
2008-04-28 9:01 ` Alan Cox
2008-04-28 9:17 ` David Miller
2008-04-28 9:48 ` Adrian Bunk
2008-04-28 11:50 ` Ingo Molnar
2008-04-28 6:10 ` Christoph Hellwig
2008-04-28 16:55 ` H. Peter Anvin
2008-04-27 22:34 ` James Bottomley
2008-04-27 22:39 ` Jeff Garzik
2008-04-27 22:44 ` H. Peter Anvin
2008-04-27 22:46 ` David Miller
2008-04-27 22:52 ` H. Peter Anvin
2008-04-27 22:58 ` David Miller
2008-04-27 23:04 ` H. Peter Anvin
2008-04-30 20:35 ` Eric W. Biederman
2008-04-27 23:34 ` Jeff Garzik
2008-04-27 23:39 ` H. Peter Anvin
2008-04-27 22:53 ` Jeff Garzik
2008-04-27 22:56 ` H. Peter Anvin
2008-04-27 22:59 ` David Miller
2008-04-27 23:02 ` Jeff Garzik
2008-04-27 23:14 ` Arjan van de Ven
2008-04-27 23:01 ` Arjan van de Ven
2008-04-30 21:44 ` James Bottomley
2008-04-30 22:39 ` H. Peter Anvin
2008-04-27 23:01 ` Thomas Gleixner
2008-04-28 14:10 ` Arjan van de Ven
2008-04-28 14:29 ` James Bottomley
2008-04-28 15:07 ` Arjan van de Ven
2008-04-28 19:59 ` H. Peter Anvin
2008-04-27 22:00 ` Breakage caused by unreviewed patch in x86 tree H. Peter Anvin
2008-04-27 22:10 ` James Bottomley
2008-04-27 22:13 ` H. Peter Anvin [this message]
2008-04-27 22:18 ` James Bottomley
2008-04-27 22:31 ` H. Peter Anvin
2008-04-27 22:58 ` Arjan van de Ven
2008-04-27 23:00 ` David Miller
2008-04-27 23:07 ` Arjan van de Ven
2008-04-27 23:03 ` James Bottomley
2008-04-27 23:11 ` Arjan van de Ven
2008-04-27 23:17 ` H. Peter Anvin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4814FAA0.8060705@zytor.com \
--to=hpa@zytor.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.