>>> On 12.08.16 at 12:03, wrote:
> On Thu, Aug 11, 2016 at 07:14:06AM -0600, Jan Beulich wrote:
>> >>> On 11.08.16 at 11:17, wrote:
>> > @@ -1404,12 +1438,20 @@ void __init noreturn __start_xen(unsigned long
> mbi_p)
>> > if ( !opt_smep )
>> > setup_clear_cpu_cap(X86_FEATURE_SMEP);
On Thu, Aug 11, 2016 at 07:14:06AM -0600, Jan Beulich wrote:
> >>> On 11.08.16 at 11:17, wrote:
> > @@ -1404,12 +1438,20 @@ void __init noreturn __start_xen(unsigned long
> > mbi_p)
> > if ( !opt_smep )
> > setup_clear_cpu_cap(X86_FEATURE_SMEP);
> > if ( cpu_has_smep )
> > +
>>> On 11.08.16 at 11:17, wrote:
> Enhance "skaj...@intel.com>mep" and "smap" command line options to support
I guess that was meant to be "smep".
> enabling SMEP
> or SMAP for HVM only with allowing "hvm" as a value.
A primary complaint of mine on v1 was not addressed: The description
continu
Enhance "skaj...@intel.com>mep" and "smap" command line options to support
enabling SMEP
or SMAP for HVM only with allowing "hvm" as a value.
Signed-off-by: He Chen
---
Changes in V2:
* Allow "hvm" as a value to "smep" and "smap" command line options.
* Clear SMEP/SMAP CPUID bits for pv guests
Enhance "smep" and "smap" command line options to support enabling SMEP
or SMAP for HVM only with allowing "hvm" as a value.
Signed-off-by: He Chen
---
Changes in V2:
* Allow "hvm" as a value to "smep" and "smap" command line options.
* Clear SMEP/SMAP CPUID bits for pv guests if they are set to
