[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1e3f7ff0-0159-98e8-ba21-8806c3a14820@redhat.com>
Date: Fri, 6 Mar 2020 06:32:49 +0100
From: Paolo Bonzini <pbonzini@...hat.com>
To: linmiaohe <linmiaohe@...wei.com>,
"vkuznets@...hat.com" <vkuznets@...hat.com>
Cc: "rkrcmar@...hat.com" <rkrcmar@...hat.com>,
"sean.j.christopherson@...el.com" <sean.j.christopherson@...el.com>,
"jmattson@...gle.com" <jmattson@...gle.com>,
"joro@...tes.org" <joro@...tes.org>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"mingo@...hat.com" <mingo@...hat.com>,
"bp@...en8.de" <bp@...en8.de>, "hpa@...or.com" <hpa@...or.com>,
"kvm@...r.kernel.org" <kvm@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"x86@...nel.org" <x86@...nel.org>
Subject: Re: [PATCH] KVM: VMX: Use wrapper macro
~RMODE_GUEST_OWNED_EFLAGS_BITS directly
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.
Paolo
Powered by blists - more mailing lists