From: Keir Fraser <keir.xen@gmail.com>
To: Jan Beulich <JBeulich@novell.com>,
Ian Campbell <Ian.Campbell@citrix.com>
Cc: Andrew Cooper <Andrew.Cooper3@citrix.com>,
xen devel <xen-devel@lists.xensource.com>
Subject: Re: APIC MSRs query
Date: Tue, 17 May 2011 15:53:46 +0100 [thread overview]
Message-ID: <C9F84A8A.1A4E9%keir.xen@gmail.com> (raw)
In-Reply-To: <4DD29D710200007800041A61@vpn.id2.novell.com>
On 17/05/2011 15:08, "Jan Beulich" <JBeulich@novell.com> wrote:
>>> I think this is a benign mistake. Benign because I don't think there is
>>> a meaningful (to Xen at least) number of systems that would not
>>> have their LAPIC at the default address (which fits in 32 bits).
>>
>> That "msr_content = (uint32_t)msr_content;" seems to be pretty
>> deliberate, what else would it be trying to do?
>>
>> FWIW enable_x2apic in Linux seems to have a similar construct which
>> throws away the top half of the MSR:
>
> Surely the Xen code got cloned from the Linux one.
If you actually look at the change in 21669:b622e411, you can see that the
above line is deliberate. The old code did wrmsr(msr, lo, 0), and clearing
upper 32 bits before calling wrmsrl() is the equivalent of that.
So this should not be 'cleaned up' without understanding that old code
(which almost certainly itself comes from Linux).
And I should also warn that I will simply ignore gratuitous cleanups in the
APIC code. The code is mostly Linux sourced, I'd rather we synced again than
diverge further.
-- Keir
prev parent reply other threads:[~2011-05-17 14:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-17 13:25 APIC MSRs query Andrew Cooper
2011-05-17 13:43 ` Jan Beulich
2011-05-17 13:49 ` Andrew Cooper
2011-05-17 13:59 ` Ian Campbell
2011-05-17 14:08 ` Andrew Cooper
2011-05-17 14:08 ` Jan Beulich
2011-05-17 14:53 ` Keir Fraser [this message]
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=C9F84A8A.1A4E9%keir.xen@gmail.com \
--to=keir.xen@gmail.com \
--cc=Andrew.Cooper3@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=JBeulich@novell.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).