Hello Jan,
I have tested your patch, it works fine in situation when cpu_has_mpx = 1 and
cpu_has_vmx_mpx = 0.
Thank you!
Best regards,
Dmitry Rockosov
> -Original Message-
> From: Jan Beulich [mailto:jbeul...@suse.com]
> Sent: Friday, August 26, 2016 11:09 AM
> To: Rockosov, Dmitry <dmitry.rocko...@intel.com>
> Cc: Andrew Cooper <andrew.coop...@citrix.com>; Sorokin, Georgy
> <georgy.soro...@intel.com>; Rechistov, Grigory
> <grigory.rechis...@intel.com>; Nakajima, Jun <jun.nakaj...@intel.com>;
> Tian, Kevin <kevin.t...@intel.com>; Kornev, Roman M
> <roman.m.kor...@intel.com>; Samoylidi, Sergey N
> <sergey.n.samoyl...@intel.com>; xen-devel@lists.xen.org
> Subject: Re: [Xen-devel] Issue in MPX support in Xen
>
> >>> On 25.08.16 at 18:53, <dmitry.rocko...@intel.com> wrote:
> > We are working on enabling XEN with WindRiver Simics, which is Intel
> > reference functional simulator for servers.
> >
> > We found the issue in XEN with MPX using.
> > If MPX is supported by CPUID, but MPX is not supported by VMX, XEN is
> > failing on store CPU MSR GUEST_BNDCFGS (file
> > xen-4.7.0/xen/arch/x86/hvm/vmx/vmx.c:798).
> >
> > SDM says in 24.4.1 Guest Register State:
> > IA32_BNDCFGS (64 bits). This field is supported only on processors
> > that support either the 1-setting of the "load IA32_BNDCFGS" VM-entry
> > control or that of the "clear IA32_BNDCFGS"
> > VM-exit control.
> >
> > Looks like XEN doesn't consult VM-entry control or VM-exit control
> > listed in SDM.
>
> Could you give the attached patch a try? It's against -unstable and will
> require trivial adjustment to two of the vmx.c hunks in order to apply
> to 4.7.
>
> Andrew, Kevin, Jun - please take a look as well, in particular regarding
> the non-commit-message remark.
>
> Jan
Joint Stock Company Intel A/O
Registered legal address: Krylatsky Hills Business Park,
17 Krylatskaya Str., Bldg 4, Moscow 121614,
Russian Federation
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
___
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
