On Monday, June 29, 2020 5:49pm, "Sean Christopherson"
said:
> On Mon, Jun 29, 2020 at 02:22:45PM -0700, Andy Lutomirski wrote:
>>
>>
>> > On Jun 29, 2020, at 1:54 PM, David P. Reed wrote:
>> >
>> > Simple question for those on the To: and CC: list here. Should I
>> > abandon any hope of
On Mon, Jun 29, 2020 at 02:22:45PM -0700, Andy Lutomirski wrote:
>
>
> > On Jun 29, 2020, at 1:54 PM, David P. Reed wrote:
> >
> > Simple question for those on the To: and CC: list here. Should I
> > abandon any hope of this patch being accepted? It's been a long time.
> >
> > The
> On Jun 29, 2020, at 1:54 PM, David P. Reed wrote:
>
> Simple question for those on the To: and CC: list here. Should I abandon any
> hope of this patch being accepted? It's been a long time.
>
> The non-response after I acknowledged that this was discovered by when
> working on a
Simple question for those on the To: and CC: list here. Should I abandon any
hope of this patch being accepted? It's been a long time.
The non-response after I acknowledged that this was discovered by when working
on a personal, non-commercial research project - which is "out-of-tree"
Correction to my comment below.
On Thursday, June 25, 2020 10:45am, "David P. Reed" said:
> [Sorry: this is resent because my mailer included HTML, rejected by LKML]
> Thanks for the response, Sean ... I had thought everyone was too busy to
> follow up
> from the first version.
>
> I confess
[Sorry: this is resent because my mailer included HTML, rejected by LKML]
Thanks for the response, Sean ... I had thought everyone was too busy to follow
up from the first version.
I confess I'm not sure why this should be broken up into a patch series, given
that it is so very small and is
On Thu, Jun 11, 2020 at 03:48:18PM -0400, David P. Reed wrote:
> -/** Disable VMX on the current CPU
> +/* Disable VMX on the current CPU
> *
> - * vmxoff causes a undefined-opcode exception if vmxon was not run
> - * on the CPU previously. Only call this function if you know VMX
> - * is
If a panic/reboot occurs when CR4 has VMX enabled, a VMXOFF is
done on all CPUS, to allow the INIT IPI to function, since
INIT is suppressed when CPUs are in VMX root operation.
Problem is that VMXOFF will causes undefined operation fault when CPU not
in VMX operation, that is, VMXON has not been
If a panic/reboot occurs when CR4 has VMX enabled, a VMXOFF is
done on all CPUS, to allow the INIT IPI to function, since
INIT is suppressed when CPUs are in VMX root operation.
Problem is that VMXOFF will causes undefined operation fault when CPU not
in VMX operation, that is, VMXON has not been
9 matches
Mail list logo
