From: Avi Kivity <avi@qumranet.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: kvm-devel@lists.sourceforge.net, qemu-devel@nongnu.org,
"Maciej W. Rozycki" <macro@linux-mips.org>,
Glauber Costa <gcosta@redhat.com>
Subject: Re: [PATCH] ignore reads to the EOI register.
Date: Thu, 27 Mar 2008 14:55:39 +0200 [thread overview]
Message-ID: <47EB994B.7080108@qumranet.com> (raw)
In-Reply-To: <87hcesjpqa.fsf@basil.nowhere.org>
Andi Kleen wrote:
> "Maciej W. Rozycki" <macro@linux-mips.org> writes:
>
>> Linux performs reads to all registers written including this one
>> deliberately using an RMW cycle to avoid triggering an erratum in some
>> early Pentium integrated APICs. Obviously it does not matter for most of
>> the world as the workaround is build-time conditional, but you'll get it
>> if you build a generic "runs everywhere" kernel.
>>
>
> It would be quite possible to make the cycle conditional on a
> cpufeatures.h quirk flag that is only set on P5. Just would need to
> out of line a few functions to avoid code bloat.
>
Or, alternatives? xchg vs mov?
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
next prev parent reply other threads:[~2008-03-27 12:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-27 0:57 [PATCH] ignore reads to the EOI register Glauber Costa
2008-03-27 8:18 ` Avi Kivity
2008-03-27 11:29 ` Maciej W. Rozycki
[not found] ` <87hcesjpqa.fsf@basil.nowhere.org>
2008-03-27 12:55 ` Avi Kivity [this message]
2008-03-27 13:36 ` Maciej W. Rozycki
2008-03-27 23:39 ` [Qemu-devel] " Aurelien Jarno
2008-03-28 12:59 ` Glauber Costa
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=47EB994B.7080108@qumranet.com \
--to=avi@qumranet.com \
--cc=andi@firstfloor.org \
--cc=gcosta@redhat.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=macro@linux-mips.org \
--cc=qemu-devel@nongnu.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox