>>> On 18.04.18 at 17:54, wrote:
> On 18/04/18 17:45, Jan Beulich wrote:
> On 18.04.18 at 17:33, wrote:
>>> On 18/04/18 17:29, Jan Beulich wrote:
>>> On 18.04.18 at 10:30, wrote:
> --- a/xen/arch/x86/mm/shadow/multi.c
> +++
>>> On 18.04.18 at 17:33, wrote:
> On 18/04/18 17:29, Jan Beulich wrote:
> On 18.04.18 at 10:30, wrote:
>>> --- a/xen/arch/x86/mm/shadow/multi.c
>>> +++ b/xen/arch/x86/mm/shadow/multi.c
>>> @@ -967,7 +967,7 @@ static int shadow_set_l4e(struct domain *d,
>>>
On 18/04/18 11:42, Sergey Dyasli wrote:
> Hi Juergen,
>
> 2 small requests from me below.
>
> On Wed, 2018-04-18 at 10:30 +0200, Juergen Gross wrote:
>> Instead of switching XPTI globally on or off add a per-domain flag for
>> that purpose. This allows to modify the xpti boot parameter to
On 18/04/18 11:49, Jan Beulich wrote:
On 18.04.18 at 11:42, wrote:
>> On Wed, 2018-04-18 at 10:30 +0200, Juergen Gross wrote:
>> @@ -119,8 +122,9 @@ static void __init print_details(enum ind_thunk thunk)
>> boot_cpu_has(X86_FEATURE_RSB_NATIVE) ? "
>>> On 18.04.18 at 11:42, wrote:
> On Wed, 2018-04-18 at 10:30 +0200, Juergen Gross wrote:
> @@ -119,8 +122,9 @@ static void __init print_details(enum ind_thunk thunk)
> boot_cpu_has(X86_FEATURE_RSB_NATIVE) ? " RSB_NATIVE" : "",
>
Hi Juergen,
2 small requests from me below.
On Wed, 2018-04-18 at 10:30 +0200, Juergen Gross wrote:
> Instead of switching XPTI globally on or off add a per-domain flag for
> that purpose. This allows to modify the xpti boot parameter to support
> running dom0 without Meltdown mitigations. Using