xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Mukesh Rathor <mukesh.rathor@oracle.com>
To: "Roger Pau Monné" <roger.pau@citrix.com>
Cc: Xen-devel@lists.xensource.com, ian.jackson@eu.citrix.com,
	ian.campbell@citrix.com, stefano.stabellini@eu.citrix.com
Subject: Re: [V0 PATCH] pvh: expose feature flags from tools for domUs
Date: Tue, 28 Jan 2014 18:33:14 -0800	[thread overview]
Message-ID: <20140128183314.0460c078@mantra.us.oracle.com> (raw)
In-Reply-To: <52E7A16F.6090401@citrix.com>

On Tue, 28 Jan 2014 13:24:15 +0100
Roger Pau Monné <roger.pau@citrix.com> wrote:

> On 25/01/14 02:13, Mukesh Rathor wrote:
> > Expose features for pvh domUs from tools.
> > 
> > Signed-off-by: Mukesh Rathor <mukesh.rathor@oracle.com>
> > ---
> >  tools/libxc/xc_cpuid_x86.c |   26 ++++++++++++++++----------
> >  tools/libxc/xc_domain.c    |    1 +
> >  tools/libxc/xenctrl.h      |    2 +-
> >  3 files changed, 18 insertions(+), 11 deletions(-)
> > 
> > diff --git a/tools/libxc/xc_cpuid_x86.c b/tools/libxc/xc_cpuid_x86.c
> > index bbbf9b8..33f6829 100644
> > --- a/tools/libxc/xc_cpuid_x86.c
> > +++ b/tools/libxc/xc_cpuid_x86.c
> > @@ -433,7 +433,7 @@ static void xc_cpuid_hvm_policy(
> >  
> >  static void xc_cpuid_pv_policy(
> >      xc_interface *xch, domid_t domid,
> > -    const unsigned int *input, unsigned int *regs)
> > +    const unsigned int *input, unsigned int *regs, int is_pvh)
> >  {
> >      DECLARE_DOMCTL;
> >      unsigned int guest_width;
> > @@ -455,13 +455,16 @@ static void xc_cpuid_pv_policy(
> >  
> >      if ( (input[0] & 0x7fffffff) == 0x00000001 )
> >      {
> > -        clear_bit(X86_FEATURE_VME, regs[3]);
> > -        clear_bit(X86_FEATURE_PSE, regs[3]);
> > -        clear_bit(X86_FEATURE_PGE, regs[3]);
> > -        clear_bit(X86_FEATURE_MCE, regs[3]);
> > -        clear_bit(X86_FEATURE_MCA, regs[3]);
> > +        if ( !is_pvh )
> > +        {
> > +            clear_bit(X86_FEATURE_VME, regs[3]);
> > +            clear_bit(X86_FEATURE_PSE, regs[3]);
> > +            clear_bit(X86_FEATURE_PGE, regs[3]);
> > +            clear_bit(X86_FEATURE_MCE, regs[3]);
> > +            clear_bit(X86_FEATURE_MCA, regs[3]);
> 
> Should we enable MCA/MCE flags for PVH DomUs? It looks to me like Dom0
> is the only domain that can make use of MCE/MCA.

Yes, PVH, like any other guest, may setup MCE handlers if they are
enabled, and xen would inject any MCE to guest if it belongs to the
guest.

thanks
Mukesh



_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  parent reply	other threads:[~2014-01-29  2:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-25  1:13 [V0 PATCH]: feature flags for PVH Mukesh Rathor
2014-01-25  1:13 ` [V0 PATCH] pvh: expose feature flags from tools for domUs Mukesh Rathor
2014-01-28 11:14   ` Ian Campbell
2014-01-29  2:31     ` Mukesh Rathor
2014-01-28 12:24   ` Roger Pau Monné
2014-01-28 12:37     ` Jan Beulich
2014-01-29  2:33     ` Mukesh Rathor [this message]
2014-02-07  1:15   ` Mukesh Rathor
2014-02-07  9:54     ` Ian Campbell
2014-02-07  8:41   ` Roger Pau Monné

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=20140128183314.0460c078@mantra.us.oracle.com \
    --to=mukesh.rathor@oracle.com \
    --cc=Xen-devel@lists.xensource.com \
    --cc=ian.campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=roger.pau@citrix.com \
    --cc=stefano.stabellini@eu.citrix.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).