From: Sergey Dyasli <sergey.dyasli@citrix.com>
To: "JBeulich@suse.com" <JBeulich@suse.com>,
Andrew Cooper <Andrew.Cooper3@citrix.com>
Cc: Sergey Dyasli <sergey.dyasli@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Roger Pau Monne <roger.pau@citrix.com>
Subject: Re: [PATCH v1] x86/msr: add Raw and Host domain policies
Date: Fri, 16 Feb 2018 10:33:52 +0000 [thread overview]
Message-ID: <1518777232.2904.1.camel@citrix.com> (raw)
In-Reply-To: <5A859A1E02000078001A8131@prv-mh.provo.novell.com>
On Thu, 2018-02-15 at 06:33 -0700, Jan Beulich wrote:
> > > > On 08.02.18 at 11:23, <sergey.dyasli@citrix.com> wrote:
> >
> > --- a/xen/arch/x86/cpu/common.c
> > +++ b/xen/arch/x86/cpu/common.c
> > @@ -118,9 +118,18 @@ void (* __read_mostly ctxt_switch_masking)(const struct vcpu *next);
> >
> > bool __init probe_cpuid_faulting(void)
> > {
> > + struct msr_domain_policy *dp = &raw_msr_domain_policy;
>
> Unless you foresee the variable to be needed for further things
> here, could this be moved into the more narrow scope it's used in
> please?
Will do in v2.
> > uint64_t val;
> > + int rc;
> >
> > - if (rdmsr_safe(MSR_INTEL_PLATFORM_INFO, val) ||
> > + if ((rc = rdmsr_safe(MSR_INTEL_PLATFORM_INFO, val)) == 0)
> > + {
> > + dp->plaform_info.available = true;
> > + if (val & MSR_PLATFORM_INFO_CPUID_FAULTING)
> > + dp->plaform_info.cpuid_faulting = true;
> > + }
> > +
> > + if (rc ||
> > !(val & MSR_PLATFORM_INFO_CPUID_FAULTING) ||
> > rdmsr_safe(MSR_INTEL_MISC_FEATURES_ENABLES,
> > this_cpu(msr_misc_features)))
>
> Below here we have
>
> setup_clear_cpu_cap(X86_FEATURE_CPUID_FAULTING);
>
> Shouldn't this be reflected in the host policy?
I guess the correct thing to do for now for host_msr_domain_policy is:
dp->plaform_info.cpuid_faulting = cpu_has_cpuid_faulting;
Looking at the code, calculate_pv_max_policy() will be simplified with
the above change: pv_max_msr_domain_policy will become a copy of host
policy.
This actually brings a question: what to do about per-pCPU MSRs in the
context of MSR policy?
--
Thanks,
Sergey
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-02-16 10:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-08 10:23 [PATCH v1] x86/msr: add Raw and Host domain policies Sergey Dyasli
2018-02-08 11:08 ` Andrew Cooper
2018-02-08 11:21 ` Roger Pau Monné
2018-02-08 11:29 ` Sergey Dyasli
2018-02-15 13:33 ` Jan Beulich
2018-02-16 10:33 ` Sergey Dyasli [this message]
2018-02-16 11:06 ` Jan Beulich
2018-02-16 11:31 ` Sergey Dyasli
2018-02-16 11:37 ` Jan Beulich
2018-02-16 11:38 ` Andrew Cooper
2018-02-16 16:00 ` Sergey Dyasli
2018-02-16 16:02 ` Andrew Cooper
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=1518777232.2904.1.camel@citrix.com \
--to=sergey.dyasli@citrix.com \
--cc=Andrew.Cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=roger.pau@citrix.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.