From: "Jan Beulich" <JBeulich@novell.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH] i386 linux: make 32-bit PAE kernel work when built with newer gcc
Date: Fri, 17 Mar 2006 13:28:51 +0100 [thread overview]
Message-ID: <441AB993.76F0.0078.0@novell.com> (raw)
In-Reply-To: <107e12b20452b34c59a79771f686802d@cl.cam.ac.uk>
>Not sure which spec you refer to but it definitely can happen, as
>demonstrated by the infamous AMD GART problem some time back:
>http://lwn.net/2002/0124/a/athlon-agp-problem.php3
>
>The above link gives plenty of detail, but briefly: The processor can
>speculatively decide it's found a store instruction and thus
>write-allocate an arbitrary cache line. This line will ultimately get
>written back even if the speculative store never actually gets
>executed.
Indeed, then this should be needed on native, too. I have to admit that
I hadn't read about x86 processors using speculative writes (Intel's SDM,
Vol 3, section 7.2.2 clearly doesn't say anything like that, and AMD doesn't
seem to have references to such behavior in their SDM either).
Jan
next prev parent reply other threads:[~2006-03-17 12:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-13 16:40 [PATCH] i386 linux: make 32-bit PAE kernel work when built with newer gcc Jan Beulich
2006-03-14 10:09 ` Keir Fraser
2006-03-14 10:40 ` Jan Beulich
2006-03-14 11:53 ` Keir Fraser
2006-03-14 12:40 ` Jan Beulich
2006-03-14 14:06 ` Keir Fraser
2006-03-14 14:31 ` Jan Beulich
2006-03-14 14:39 ` Keir Fraser
2006-03-17 10:19 ` Keir Fraser
2006-03-17 11:35 ` Jan Beulich
2006-03-17 11:51 ` Keir Fraser
2006-03-17 12:28 ` Jan Beulich [this message]
2006-03-17 13:24 ` Keir Fraser
2006-03-17 13:37 ` Jan Beulich
-- strict thread matches above, loose matches on Subject: below --
2006-03-14 12:15 Petersson, Mats
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=441AB993.76F0.0078.0@novell.com \
--to=jbeulich@novell.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=xen-devel@lists.xensource.com \
/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.