[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <jpgd1eg20mx.fsf@linux.bootlegged.copy>
Date: Fri, 17 Feb 2017 12:22:14 -0500
From: Bandan Das <bsd@...hat.com>
To: Paolo Bonzini <pbonzini@...hat.com>
Cc: linux-kernel@...r.kernel.org, kvm@...r.kernel.org
Subject: Re: [PATCH] KVM: VMX: use vmcs_set/clear_bits for CPU-based execution controls
Paolo Bonzini <pbonzini@...hat.com> writes:
> ----- Original Message -----
>> From: "Bandan Das" <bsd@...hat.com>
>> To: "Paolo Bonzini" <pbonzini@...hat.com>
>> Cc: linux-kernel@...r.kernel.org, kvm@...r.kernel.org
>> Sent: Friday, February 17, 2017 1:04:14 AM
>> Subject: Re: [PATCH] KVM: VMX: use vmcs_set/clear_bits for CPU-based execution controls
>>
>> Paolo Bonzini <pbonzini@...hat.com> writes:
>>
>> > Signed-off-by: Paolo Bonzini <pbonzini@...hat.com>
>> > ---
>>
>> I took a quick look and found these two potential
>> consumers of these set/clear wrappers.
>>
>> vmcs_set_secondary_exec_control()
>> vmx_set_virtual_x2apic_mode()
>>
>> Since this has been reviewed already,
>> we can just have them later in a follow up
>> (unless you left them out intentionally).
>
> Both of these can both set and clear bits, so they could be the
> consumer of a new function
>
> void vmcs_write_bits(u16 field, u32 value, u32 mask)
>
> but I don't see much benefit in introducing it; the cognitive
> load is higher than vmcs_{set,clear}_bits.
Yes, agreed. Thanks!
> Paolo
Powered by blists - more mailing lists