All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zhao Liu <zhao1.liu@intel.com>
To: Aidan Khoury <aidan@aktech.ai>
Cc: qemu-devel@nongnu.org, aidan@revers.engineering,
	Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH] i386/cpu: Fix unexpected initializer override in CPU model definition for Diamond Rapids
Date: Fri, 23 Jan 2026 18:24:24 +0800	[thread overview]
Message-ID: <aXNMWKq7ecx/9CXj@intel.com> (raw)
In-Reply-To: <20260113164355.1623966-2-aidan@aktech.ai>

(Cc Maintainer Paolo)

On Tue, Jan 13, 2026 at 12:43:56PM -0400, Aidan Khoury wrote:
> Date: Tue, 13 Jan 2026 12:43:56 -0400
> From: Aidan Khoury <aidan@aktech.ai>
> Subject: [PATCH] i386/cpu: Fix unexpected initializer override in CPU model
>  definition for Diamond Rapids
> X-Mailer: git-send-email 2.43.0
> 
> The new Diamond Rapids x86 cpu model definition that was added in 7a6dd8bde159 has an unexpected comma in
> the `.features[FEAT_VMX_EXIT_CTLS]` subobject initializer causing the prior initialization to be overridden,
> meaning that `VMX_VM_EXIT_SAVE_DEBUG_CONTROLS | VMX_VM_EXIT_HOST_ADDR_SPACE_SIZE` is not included.
> 
> Fix this by replacing the comma with the missing bitwise OR to properly combine all the flags into a single
> bitmask value.
> 
> Fixes: 7a6dd8bde159 ("i386/cpu: Add CPU model for Diamond Rapids")
> Signed-off-by: Aidan Khoury <aidan@aktech.ai>
> ---
>  target/i386/cpu.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

Thank you and my bad,

Reviewed-by: Zhao Liu <zhao1.liu@intel.com>

BTW, just curious, what warning did you meet? I can make some
improvements.

Thanks,
Zhao



      reply	other threads:[~2026-01-23  9:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-13 16:43 [PATCH] i386/cpu: Fix unexpected initializer override in CPU model definition for Diamond Rapids Aidan Khoury
2026-01-23 10:24 ` Zhao Liu [this message]

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=aXNMWKq7ecx/9CXj@intel.com \
    --to=zhao1.liu@intel.com \
    --cc=aidan@aktech.ai \
    --cc=aidan@revers.engineering \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.