qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Xiaoyao Li <xiaoyao.li@intel.com>
To: "Paolo Bonzini" <pbonzini@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>,
	"Peter Maydell" <peter.maydell@linaro.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH 2/2] target/i386: Use X86ASIdx_MEM in kvm_init()
Date: Thu, 16 Oct 2025 17:46:32 +0800	[thread overview]
Message-ID: <d0494262-a805-4311-bcb1-c47bdf1f0eac@intel.com> (raw)
In-Reply-To: <af20ba0c-26ad-48d7-a135-918f14b8d63e@redhat.com>

On 10/16/2025 5:23 PM, Paolo Bonzini wrote:
> On 10/16/25 10:43, Philippe Mathieu-Daudé wrote:
>> On 14/10/25 11:42, Xiaoyao Li wrote:
>>> When the patch introduces 'enum X86ADIdx'[0] got merged, it somehow
>>> missed the change to replace as id 0 with X86ASIdx_MEM in kvm_init().
> 
> It wasn't missed, it broke CI. ;)

I see.

I missed the fact that Philippe pointed out:

   this is a generic code use by multiple architectures.

Sorry for the wrong patch.

> Paolo
> 
>>> Change the leftover in kvm_init() to make the usage consistent.
>>>
>>> [0] https://lore.kernel.org/qemu-devel/20250730095253.1833411-3- 
>>> xiaoyao.li@intel.com/
>>>
>>> Signed-off-by: Xiaoyao Li <xiaoyao.li@intel.com>
>>> ---
>>>   accel/kvm/kvm-all.c | 2 +-
>>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/accel/kvm/kvm-all.c b/accel/kvm/kvm-all.c
>>> index 58802f7c3cc1..3030c47d55b1 100644
>>> --- a/accel/kvm/kvm-all.c
>>> +++ b/accel/kvm/kvm-all.c
>>> @@ -2800,7 +2800,7 @@ static int kvm_init(AccelState *as, 
>>> MachineState *ms)
>>>       s->memory_listener.listener.coalesced_io_del = 
>>> kvm_uncoalesce_mmio_region;
>>>       kvm_memory_listener_register(s, &s->memory_listener,
>>> -                                 &address_space_memory, 0, "kvm- 
>>> memory");
>>> +                                 &address_space_memory, 
>>> X86ASIdx_MEM, "kvm-memory");
>>
>> NAck: this is a generic code use by multiple architectures.
>>
>>
> 



      reply	other threads:[~2025-10-16  9:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-14  9:42 [PATCH 0/2] x86/cpu: initialize SMM cpu address space for hotplugged cpus Xiaoyao Li
2025-10-14  9:42 ` [PATCH 1/2] i386/kvm/cpu: Init SMM cpu address space for hotplugged CPUs Xiaoyao Li
2025-10-14  9:42 ` [PATCH 2/2] target/i386: Use X86ASIdx_MEM in kvm_init() Xiaoyao Li
2025-10-16  8:43   ` Philippe Mathieu-Daudé
2025-10-16  9:23     ` Paolo Bonzini
2025-10-16  9:46       ` Xiaoyao Li [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=d0494262-a805-4311-bcb1-c47bdf1f0eac@intel.com \
    --to=xiaoyao.li@intel.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@linaro.org \
    --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 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).