From: Razvan Cojocaru <rzvncj@gmail.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: How to get a few MSR values from userspace?
Date: Fri, 21 Dec 2012 16:08:53 +0200 [thread overview]
Message-ID: <50D46D75.1010800@gmail.com> (raw)
In-Reply-To: <50D4780602000078000B204E@nat28.tlf.novell.com>
>> I need access to some MSR values that are not currently being saved in
>> struct hvm_hw_cpu. Among them are MSR_IA32_MC0_CTL, MSR_IA32_MISC_ENABLE
>> and MSR_IA32_ENERGY_PERF_BIAS.
>
> I can't see why, and this is quite likely related to the reason for
> them not being accessible in the first place.
Because they offer heuristic information about the type of OS running in
the domU domain, and there are classes of applications interested in that.
> Not to me, no. These records are use for save/restore/migrate,
> and so far there hasn't been a need to include here the MSRs you
> mention.
Interesting. I've assumed that those would be saved (and perhaps ignored
on restore if they became irrelevant) in a migration scenario.
> For MSR_IA32_MC0_CTL, why not? These should be fine for
> anything that is architectural to x86.
>
> The other two MSRs are Intel specific iirc, and hence wouldn't
> be validly dealt with in vendor independent code.
I agree, however, as I've said before, _some_ applications _are_
interested in vendor-specific information for heuristic purposes.
Whether this would make a interesting patch for Xen or not, I would
appreciate any advice on how best to implement said functionality (if
only for MSR_IA32_MC0_CTL).
Thanks,
Razvan Cojocaru
next prev parent reply other threads:[~2012-12-21 14:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-21 12:45 How to get a few MSR values from userspace? Razvan Cojocaru
2012-12-21 13:16 ` Mats Petersson
2012-12-21 13:26 ` Razvan Cojocaru
2012-12-21 13:53 ` Jan Beulich
2012-12-21 14:08 ` Razvan Cojocaru [this message]
2012-12-21 14:39 ` Mats Petersson
2012-12-21 16:01 ` Jan Beulich
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=50D46D75.1010800@gmail.com \
--to=rzvncj@gmail.com \
--cc=JBeulich@suse.com \
--cc=xen-devel@lists.xen.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 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.