[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87sgiles16.fsf@vitty.brq.redhat.com>
Date: Fri, 06 Mar 2020 10:44:53 +0100
From: Vitaly Kuznetsov <vkuznets@...hat.com>
To: Paolo Bonzini <pbonzini@...hat.com>,
linmiaohe <linmiaohe@...wei.com>
Cc: "rkrcmar\@redhat.com" <rkrcmar@...hat.com>,
"sean.j.christopherson\@intel.com" <sean.j.christopherson@...el.com>,
"jmattson\@google.com" <jmattson@...gle.com>,
"joro\@8bytes.org" <joro@...tes.org>,
"tglx\@linutronix.de" <tglx@...utronix.de>,
"mingo\@redhat.com" <mingo@...hat.com>,
"bp\@alien8.de" <bp@...en8.de>, "hpa\@zytor.com" <hpa@...or.com>,
"kvm\@vger.kernel.org" <kvm@...r.kernel.org>,
"linux-kernel\@vger.kernel.org" <linux-kernel@...r.kernel.org>,
"x86\@kernel.org" <x86@...nel.org>
Subject: Re: [PATCH] KVM: VMX: Use wrapper macro ~RMODE_GUEST_OWNED_EFLAGS_BITS directly
Paolo Bonzini <pbonzini@...hat.com> writes:
> On 06/03/20 03:17, linmiaohe wrote:
>> Define a macro RMODE_HOST_OWNED_EFLAGS_BITS for (X86_EFLAGS_IOPL |
>> X86_EFLAGS_VM) as suggested by Vitaly seems a good way to fix this ?
>> Thanks.
>
> No, what if a host-owned flag was zero? I'd just leave it as is.
>
I'm not saying my suggestion was a good idea but honestly I'm failing to
wrap my head around this. The suggested 'RMODE_HOST_OWNED_EFLAGS_BITS'
would just be a define for (X86_EFLAGS_IOPL | X86_EFLAGS_VM) so
technically the patch would just be nop, no?
--
Vitaly
Powered by blists - more mailing lists