From: Paolo Bonzini <pbonzini@redhat.com>
To: Robert Hoo <robert.hu@linux.intel.com>,
seanjc@google.com, vkuznets@redhat.com, wanpengli@tencent.com,
jmattson@google.com, joro@8bytes.org
Cc: kvm@vger.kernel.org, yu.c.zhang@linux.intel.com
Subject: Re: [PATCH v1 1/5] KVM: x86: nVMX: Add vmcs12 field existence bitmap in nested_vmx
Date: Wed, 20 Oct 2021 17:10:28 +0200 [thread overview]
Message-ID: <b2aebaba-92bc-865d-5d52-6810ba08ceaa@redhat.com> (raw)
In-Reply-To: <1629192673-9911-2-git-send-email-robert.hu@linux.intel.com>
On 17/08/21 11:31, Robert Hoo wrote:
> +#define FIELD_BIT_SET(name, bitmap) set_bit(f_pos(name), bitmap)
> +#define FIELD64_BIT_SET(name, bitmap) \
> + do {set_bit(f_pos(name), bitmap); \
> + set_bit(f_pos(name) + (sizeof(u32) / sizeof(u16)), bitmap);\
> + } while (0)
> +
> +#define FIELD_BIT_CLEAR(name, bitmap) clear_bit(f_pos(name), bitmap)
> +#define FIELD64_BIT_CLEAR(name, bitmap) \
> + do {clear_bit(f_pos(name), bitmap); \
> + clear_bit(f_pos(name) + (sizeof(u32) / sizeof(u16)), bitmap);\
> + } while (0)
> +
> +#define FIELD_BIT_CHANGE(name, bitmap) change_bit(f_pos(name), bitmap)
> +#define FIELD64_BIT_CHANGE(name, bitmap) \
> + do {change_bit(f_pos(name), bitmap); \
> + change_bit(f_pos(name) + (sizeof(u32) / sizeof(u16)), bitmap);\
> + } while (0)
> +
> +/*
Hi Robert,
I'd rather not have FIELD_BIT_CHANGE, and instead have something like
#define FIELD_BIT_ASSIGN(name, bitmap, value) \
if (value) \
FIELD_BIT_SET(name, bitmap); \
else
FIELD_BIT_CLEAR(name, bitmap);
Also, these set_bit/clear_bit can use the non-atomic variants __set_bit
and __clear_bit, because the bitmaps are protected by the vCPU mutex.
> + FIELD64_BIT_CHANGE(posted_intr_desc_addr, bitmap);
Many of the fields you mark as 64-bit are actually natural sized.
> + if ((old_val ^ new_val) &
> + CPU_BASED_ACTIVATE_SECONDARY_CONTROLS) {
> + FIELD_BIT_CHANGE(secondary_vm_exec_control, bitmap);
> + }
> +}
If secondary controls are not available, you should treat the
corresponding MSR as if it was all zeroes. Likewise if VMFUNC is disabled.
> + if ((old_val ^ new_val) & SECONDARY_EXEC_PAUSE_LOOP_EXITING) {
> + FIELD64_BIT_CHANGE(vmread_bitmap, bitmap);
> + FIELD64_BIT_CHANGE(vmwrite_bitmap, bitmap);
This seems wrong.
Paolo
next prev parent reply other threads:[~2021-10-20 15:10 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-17 9:31 [PATCH v1 0/5] KVM/x86/nVMX: Add field existence support in VMCS12 Robert Hoo
2021-08-17 9:31 ` [PATCH v1 1/5] KVM: x86: nVMX: Add vmcs12 field existence bitmap in nested_vmx Robert Hoo
2021-10-20 15:10 ` Paolo Bonzini [this message]
2021-10-21 12:41 ` Robert Hoo
2021-08-17 9:31 ` [PATCH v1 2/5] KVM: x86: nVMX: Update VMCS12 fields existence when nVMX MSRs are set Robert Hoo
2021-10-20 15:11 ` Paolo Bonzini
2021-10-21 13:08 ` Robert Hoo
2021-08-17 9:31 ` [PATCH v1 3/5] KVM: x86: nVMX: VMCS12 field's read/write respects field existence bitmap Robert Hoo
2021-08-17 15:54 ` Sean Christopherson
2021-08-18 5:50 ` Robert Hoo
2021-08-18 23:10 ` Sean Christopherson
2021-08-18 23:45 ` Jim Mattson
2021-08-18 23:49 ` Sean Christopherson
2021-08-19 9:58 ` Robert Hoo
2021-09-01 20:42 ` Sean Christopherson
2021-09-03 8:51 ` Robert Hoo
2021-09-03 15:11 ` Sean Christopherson
2021-09-28 10:05 ` Robert Hoo
2021-10-05 16:15 ` Sean Christopherson
2021-10-05 17:32 ` Jim Mattson
2021-10-05 17:59 ` Sean Christopherson
2021-10-05 20:42 ` Jim Mattson
2021-10-05 20:50 ` Sean Christopherson
2021-10-05 22:40 ` Jim Mattson
2021-10-05 23:22 ` Sean Christopherson
2021-10-08 8:23 ` Yu Zhang
2021-10-08 15:09 ` Robert Hoo
2021-10-08 23:49 ` Jim Mattson
2021-10-09 0:05 ` Robert Hoo
2021-10-29 19:53 ` Jim Mattson
2021-11-03 1:31 ` Robert Hoo
2021-11-09 22:33 ` Sean Christopherson
2021-11-10 5:35 ` Yu Zhang
2021-11-18 1:19 ` Sean Christopherson
2021-11-19 7:32 ` Robert Hoo
2021-08-17 9:31 ` [PATCH v1 4/5] KVM: x86: nVMX: Respect vmcs12 field existence when calc vmx_vmcs_enum_msr Robert Hoo
2021-08-17 9:31 ` [PATCH v1 5/5] KVM: x86: nVMX: Ignore user space set value to MSR_IA32_VMX_VMCS_ENUM Robert Hoo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b2aebaba-92bc-865d-5d52-6810ba08ceaa@redhat.com \
--to=pbonzini@redhat.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=robert.hu@linux.intel.com \
--cc=seanjc@google.com \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.com \
--cc=yu.c.zhang@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).