[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] x86/nestedhvm: process the MSR-load and MSR-store areas of L1's VMCS


  • To: Mahmoud Abumandour <ma.mandourr@xxxxxxxxx>
  • From: Jan Beulich <jbeulich@xxxxxxxx>
  • Date: Wed, 11 Nov 2026 10:00:14 +0100
  • Authentication-results: eu.smtp.expurgate.cloud; dkim=pass header.s=google header.d=suse.com header.i="@suse.com" header.h="Content-Transfer-Encoding:Content-Type:In-Reply-To:Autocrypt:From:Content-Language:References:Cc:To:Subject:User-Agent:MIME-Version:Date:Message-ID"
  • Autocrypt: addr=jbeulich@xxxxxxxx; keydata= xsDiBFk3nEQRBADAEaSw6zC/EJkiwGPXbWtPxl2xCdSoeepS07jW8UgcHNurfHvUzogEq5xk hu507c3BarVjyWCJOylMNR98Yd8VqD9UfmX0Hb8/BrA+Hl6/DB/eqGptrf4BSRwcZQM32aZK 7Pj2XbGWIUrZrd70x1eAP9QE3P79Y2oLrsCgbZJfEwCgvz9JjGmQqQkRiTVzlZVCJYcyGGsD /0tbFCzD2h20ahe8rC1gbb3K3qk+LpBtvjBu1RY9drYk0NymiGbJWZgab6t1jM7sk2vuf0Py O9Hf9XBmK0uE9IgMaiCpc32XV9oASz6UJebwkX+zF2jG5I1BfnO9g7KlotcA/v5ClMjgo6Gl MDY4HxoSRu3i1cqqSDtVlt+AOVBJBACrZcnHAUSuCXBPy0jOlBhxPqRWv6ND4c9PH1xjQ3NP nxJuMBS8rnNg22uyfAgmBKNLpLgAGVRMZGaGoJObGf72s6TeIqKJo/LtggAS9qAUiuKVnygo 3wjfkS9A3DRO+SpU7JqWdsveeIQyeyEJ/8PTowmSQLakF+3fote9ybzd880fSmFuIEJldWxp Y2ggPGpiZXVsaWNoQHN1c2UuY29tPsJgBBMRAgAgBQJZN5xEAhsDBgsJCAcDAgQVAggDBBYC AwECHgECF4AACgkQoDSui/t3IH4J+wCfQ5jHdEjCRHj23O/5ttg9r9OIruwAn3103WUITZee e7Sbg12UgcQ5lv7SzsFNBFk3nEQQCACCuTjCjFOUdi5Nm244F+78kLghRcin/awv+IrTcIWF hUpSs1Y91iQQ7KItirz5uwCPlwejSJDQJLIS+QtJHaXDXeV6NI0Uef1hP20+y8qydDiVkv6l IreXjTb7DvksRgJNvCkWtYnlS3mYvQ9NzS9PhyALWbXnH6sIJd2O9lKS1Mrfq+y0IXCP10eS FFGg+Av3IQeFatkJAyju0PPthyTqxSI4lZYuJVPknzgaeuJv/2NccrPvmeDg6Coe7ZIeQ8Yj t0ARxu2xytAkkLCel1Lz1WLmwLstV30g80nkgZf/wr+/BXJW/oIvRlonUkxv+IbBM3dX2OV8 AmRv1ySWPTP7AAMFB/9PQK/VtlNUJvg8GXj9ootzrteGfVZVVT4XBJkfwBcpC/XcPzldjv+3 HYudvpdNK3lLujXeA5fLOH+Z/G9WBc5pFVSMocI71I8bT8lIAzreg0WvkWg5V2WZsUMlnDL9 mpwIGFhlbM3gfDMs7MPMu8YQRFVdUvtSpaAs8OFfGQ0ia3LGZcjA6Ik2+xcqscEJzNH+qh8V m5jjp28yZgaqTaRbg3M/+MTbMpicpZuqF4rnB0AQD12/3BNWDR6bmh+EkYSMcEIpQmBM51qM EKYTQGybRCjpnKHGOxG0rfFY1085mBDZCH5Kx0cl0HVJuQKC+dV2ZY5AqjcKwAxpE75MLFkr wkkEGBECAAkFAlk3nEQCGwwACgkQoDSui/t3IH7nnwCfcJWUDUFKdCsBH/E5d+0ZnMQi+G0A nAuWpQkjM1ASeQwSHEeAWPgskBQL
  • Cc: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>, Roger Pau Monné <roger@xxxxxxxxxxxxxx>, Teddy Astie <teddy.astie@xxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxxx
  • Delivery-date: Wed, 11 Nov 2026 09:00:30 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>

On 10.11.2026 07:33, Mahmoud Abumandour wrote:
> Nothing in vvmx.c reads the VM-entry MSR-load, VM-exit MSR-store or VM-exit
> MSR-load area of L1's VMCS, so L2 runs with the listed MSRs as the previous
> L2 or L1 left them, and L1 gets neither L2's values stored nor its own
> loaded back. Process each area where the SDM does, with the SDM's checks,
> an entry as a WRMSR or RDMSR at CPL 0 that L1 does not intercept. A bad
> VM-entry entry fails the VM entry with exit reason 34 and leaves the VMCS
> unlaunched, a bad VM-exit entry is a VMX abort, which crashes the domain,
> and IA32_VMX_MISC now recommends the 512 entries an area may hold.
> 
> Fixes: 9390642b7fa5 ("Nested VMX: Switch shadow/virtual VMCS between n1/n2 
> guests.")
> Assisted-by: Claude:claude-opus-5-5
> Signed-off-by: Mahmoud Abumandour <ma.mandourr@xxxxxxxxx>

Just a couple of mechanical remarks here for the moment:

> @@ -1212,11 +1214,67 @@ static void nvmx_clear_vmcs_pointer(struct vcpu *v, 
> struct vmcs_struct *vvmcs)
>      __vmwrite(VMWRITE_BITMAP, 0);
>  }
>  
> -static void virtual_vmentry(struct cpu_user_regs *regs)
> +/* The longest MSR list that IA32_VMX_MISC recommends to L1. */
> +#define NVMX_MAX_MSRS 512
> +
> +/* A nonempty MSR area must be 16-byte aligned and within MAXPHYADDR. */
> +static bool msr_area_valid(const struct vcpu *v, unsigned int addr_field,
> +                           unsigned int count_field)
> +{
> +    uint64_t addr = get_vvmcs(v, addr_field);
> +    uint64_t count = get_vvmcs(v, count_field);

Please see ./CODING_STYLE for the use of fixed-width types. "addr" likely
wants to be paddr_t, and for "count" unsigned int looks to suffice. Once
changed that way, ...

> +    unsigned int width = v->domain->arch.cpuid->extd.maxphysaddr;
> +
> +    return !count ||
> +           (!(addr & 0xf) && !(addr >> width) &&
> +            !((addr + count * sizeof(struct vmx_msr_entry) - 1) >> width));

... it'll also become clear that the multiplication here cannot overflow
(if that was possible, your check here would be insufficient).

> +/*
> + * Load or store an MSR area of L1's VMCS, each entry as an unintercepted
> + * WRMSR or RDMSR.  Returns 0, or the 1-based index of the failing entry.
> + */
> +static unsigned int process_msr_area(struct vcpu *v, unsigned int addr_field,
> +                                     unsigned int count_field)

"Load or store ..." in the comment is a little odd; the function name
using "process" better describes the purpose of the function. Maybe
"Process an MSR load or store area ..."?

> +{
> +    paddr_t addr = get_vvmcs(v, addr_field);
> +    unsigned int i, count = get_vvmcs(v, count_field);

Interestingly here you already use unsigned int.

Jan



 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.