From: Igor Mammedov <imammedo@redhat.com>
To: "Moger, Babu" <babu.moger@amd.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH 0/2] i386: fixup number of logical CPUs when host-cache-info=on
Date: Wed, 25 May 2022 09:05:06 +0200 [thread overview]
Message-ID: <20220525090506.63f55b4c@redhat.com> (raw)
In-Reply-To: <e4df1ba6-1a11-21e8-e344-f5e24fa49ce8@amd.com>
On Tue, 24 May 2022 14:48:29 -0500
"Moger, Babu" <babu.moger@amd.com> wrote:
> On 5/24/22 10:19, Igor Mammedov wrote:
> > On Tue, 24 May 2022 11:10:18 -0400
> > Igor Mammedov <imammedo@redhat.com> wrote:
> >
> > CCing AMD folks as that might be of interest to them
>
> I am trying to recreate the bug on my AMD system here.. Seeing this message..
>
> qemu-system-x86_64: -numa node,nodeid=0,memdev=ram-node0: memdev=ram-node0
> is ambiguous
>
> Here is my command line..
>
> #qemu-system-x86_64 -name rhel8 -m 4096 -hda vdisk.qcow2 -enable-kvm -net
> nic -nographic -machine q35,accel=kvm -cpu
> host,host-cache-info=on,l3-cache=off -smp
> 20,sockets=2,dies=1,cores=10,threads=1 -numa
> node,nodeid=0,memdev=ram-node0 -numa node,nodeid=1,memdev=ram-node1 -numa
> cpu,socket-id=0,node-id=0 -numa cpu,socket-id=1,node-id=1
>
> Am I missing something?
Yep, sorry I've omitted -object memory-backend-foo definitions for
ram-node0 and ram-node1
one can use any memory backend, it doesn't really matter in this case,
for example following should do:
-object memory-backend-ram,id=ram-node0,size=2G \
-object memory-backend-ram,id=ram-node1,size=2G
>
>
> >
> >> Igor Mammedov (2):
> >> x86: cpu: make sure number of addressable IDs for processor cores
> >> meets the spec
> >> x86: cpu: fixup number of addressable IDs for logical processors
> >> sharing cache
> >>
> >> target/i386/cpu.c | 20 ++++++++++++++++----
> >> 1 file changed, 16 insertions(+), 4 deletions(-)
> >>
next prev parent reply other threads:[~2022-05-25 7:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-24 15:10 [PATCH 0/2] i386: fixup number of logical CPUs when host-cache-info=on Igor Mammedov
2022-05-24 15:10 ` [PATCH 1/2] x86: cpu: make sure number of addressable IDs for processor cores meets the spec Igor Mammedov
2022-05-24 15:10 ` [PATCH 2/2] x86: cpu: fixup number of addressable IDs for logical processors sharing cache Igor Mammedov
2022-05-24 15:19 ` [PATCH 0/2] i386: fixup number of logical CPUs when host-cache-info=on Igor Mammedov
2022-05-24 19:48 ` Moger, Babu
2022-05-24 23:23 ` Alejandro Jimenez
2022-05-25 19:56 ` Moger, Babu
2022-05-25 21:20 ` Alejandro Jimenez
2022-05-25 7:05 ` Igor Mammedov [this message]
2022-05-25 20:04 ` Moger, Babu
2022-05-31 12:44 ` Igor Mammedov
2022-06-01 10:02 ` Paolo Bonzini
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=20220525090506.63f55b4c@redhat.com \
--to=imammedo@redhat.com \
--cc=babu.moger@amd.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 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).