From: "Jan Beulich" <JBeulich@novell.com>
To: Gang Wei <gang.wei@intel.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Keir Fraser <Keir.Fraser@eu.citrix.com>
Subject: RE: [PATCH] Allow dom0 to write MSR IA32_ENERGY_PERF_BIAS
Date: Wed, 05 Jan 2011 07:59:54 +0000 [thread overview]
Message-ID: <4D24330A020000780002A610@vpn.id2.novell.com> (raw)
In-Reply-To: <F26D193E20BBDC42A43B611D1BDEDE71251422920D@shsmsx502.ccr.corp.intel.com>
>>> On 05.01.11 at 03:08, "Wei, Gang" <gang.wei@intel.com> wrote:
> Jan Beulich wrote on 2011-01-04:
>>> diff -r 4e108cf56d07 xen/arch/x86/traps.c
>>> --- a/xen/arch/x86/traps.c Mon Dec 27 08:00:09 2010 +0000
>>> +++ b/xen/arch/x86/traps.c Sat Jan 01 20:01:43 2011 +0800
>>> @@ -2333,6 +2333,7 @@ static int emulate_privileged_op(struct
>>> goto fail;
>>> break;
>>> case MSR_IA32_THERM_CONTROL:
>>> + case MSR_IA32_ENERGY_PERF_BIAS:
>>> if ( boot_cpu_data.x86_vendor != X86_VENDOR_INTEL )
>>> goto fail;
>>> if ( (v->domain->domain_id != 0) ||
>>> !v->domain->is_pinned
>>> )
>>
>> Why would you allow this only if Dom0 has its vcpus pinned?
>
> It is meaningless if dom0 can't control all pcpus exactly. Only in case of
> dom0 vcpus pinned, it makes sense.
Disagree. The user mode tool could set its own affinity (virtual and
physical) and then issue the MSR write. Please don't enforce
restrictions where not really needed (I actually suppose that the
restriction should be removed for MSR_IA32_THERM_CONTROL too).
Jan
next prev parent reply other threads:[~2011-01-05 7:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-04 3:04 [PATCH] Allow dom0 to write MSR IA32_ENERGY_PERF_BIAS Wei, Gang
2011-01-04 9:58 ` Jan Beulich
2011-01-05 2:08 ` Wei, Gang
2011-01-05 7:59 ` Jan Beulich [this message]
2011-01-05 8:13 ` Keir Fraser
2011-01-05 8:17 ` Jan Beulich
2011-01-05 8:22 ` Keir Fraser
2011-01-05 8:31 ` Jan Beulich
2011-01-05 8:55 ` Wei, Gang
2011-01-05 9:03 ` 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=4D24330A020000780002A610@vpn.id2.novell.com \
--to=jbeulich@novell.com \
--cc=Keir.Fraser@eu.citrix.com \
--cc=gang.wei@intel.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).