From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "Liu, Jinsong" <jinsong.liu@intel.com>
Cc: "keir@xen.org" <keir@xen.org>,
"Ian.Campbell@citrix.com" <Ian.Campbell@citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
"haoxudong.hao@gmail.com" <haoxudong.hao@gmail.com>,
Jan Beulich <jbeulich@suse.com>
Subject: Re: [PATCH 3/4 V3] X86: MPX IA32_BNDCFGS msr handle
Date: Wed, 27 Nov 2013 09:50:05 -0500 [thread overview]
Message-ID: <20131127145005.GJ4430@pegasus.dumpdata.com> (raw)
In-Reply-To: <DE8DF0795D48FD4CA783C40EC8292335013E8099@SHSMSX101.ccr.corp.intel.com>
> >>>> Unlikely, but in case VMX support is not available, not expose
> >>>> MPX to hvm guest.
> >>> You are still missing the point.
> >>>
> >>> I as the administrator choose to prevent an HVM guest from using
> >>> MPX. Perhaps I want to create a heterogeneous pool.
> >>>
> >>> Therefore, the bit is disabled in the domains cpuid policy, despite
> >>> being available on the hardware.
> >>>
> >>> ~Andrew
> >>>
> >> Could you tell me the reason why choose to prevent HVM from using
> >> MPX?
> >>
> >> Thanks,
> >> Jinsong
> >
> > For exactly the case I gave - a VM in a heterogeneous pool where one
> > server supports MPX and the other is lacking the MPX feature.
> >
> > ~Andrew
> >
>
> I didn't see the point of your case to prevent HVM MPX feature.
> Could you elaborate more of your concern?
B/c the other nodes (that you migrate to) don't support the MPX and the
guest will crash when it tries to use it.
next prev parent reply other threads:[~2013-11-27 14:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-27 13:50 [PATCH 3/4 V3] X86: MPX IA32_BNDCFGS msr handle Liu, Jinsong
2013-11-27 13:57 ` Andrew Cooper
2013-11-27 14:04 ` Jan Beulich
2013-11-27 14:27 ` Liu, Jinsong
2013-11-27 14:31 ` Andrew Cooper
2013-11-27 14:37 ` Liu, Jinsong
2013-11-27 14:50 ` Konrad Rzeszutek Wilk [this message]
2013-11-27 14:51 ` Andrew Cooper
2013-11-27 15:02 ` Liu, Jinsong
2013-11-27 16:03 ` Andrew Cooper
2013-11-28 3:17 ` Liu, Jinsong
2013-11-28 10:34 ` Tim Deegan
2013-11-28 11:12 ` Liu, Jinsong
2013-11-28 11:14 ` Tim Deegan
2013-11-28 11:18 ` Liu, Jinsong
2013-11-28 11:26 ` Ian Campbell
2013-11-28 11:45 ` Tim Deegan
2013-11-29 9:48 ` Jan Beulich
2013-11-27 14:00 ` 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=20131127145005.GJ4430@pegasus.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=Ian.Campbell@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=haoxudong.hao@gmail.com \
--cc=jbeulich@suse.com \
--cc=jinsong.liu@intel.com \
--cc=keir@xen.org \
--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.