From: "Radim Krčmář" <rkrcmar@redhat.com>
To: "Moger, Babu" <Babu.Moger@amd.com>
Cc: "ehabkost@redhat.com" <ehabkost@redhat.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"mtosatti@redhat.com" <mtosatti@redhat.com>,
"Hook, Gary" <Gary.Hook@amd.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"pbonzini@redhat.com" <pbonzini@redhat.com>,
"pixo@polepetko.eu" <pixo@polepetko.eu>,
"rth@twiddle.net" <rth@twiddle.net>
Subject: Re: [PATCH v2 3/5] target/i386: Add support for CPUID_8000_001E for AMD
Date: Thu, 1 Mar 2018 20:57:16 +0100 [thread overview]
Message-ID: <20180301195715.GA28948@flask> (raw)
In-Reply-To: <CY4PR12MB1768464C5ABB828EEA45166B95C70@CY4PR12MB1768.namprd12.prod.outlook.com>
2018-02-28 22:18+0000, Moger, Babu:
> > -----Original Message-----
> > From: Radim Krčmář [mailto:rkrcmar@redhat.com]
> > Sent: Wednesday, February 28, 2018 12:24 PM
> > To: Moger, Babu <Babu.Moger@amd.com>
> > Cc: pbonzini@redhat.com; rth@twiddle.net; ehabkost@redhat.com;
> > mtosatti@redhat.com; qemu-devel@nongnu.org; kvm@vger.kernel.org;
> > pixo@polepetko.eu; Hook, Gary <Gary.Hook@amd.com>
> > Subject: Re: [PATCH v2 3/5] target/i386: Add support for CPUID_8000_001E
> > for AMD
> >
> > 2018-02-23 21:30-0500, Babu Moger:
> > > From: Stanislav Lanci <pixo@polepetko.eu>
> > >
> > > Populate threads/core_id/apic_ids/socket_id when CPUID_EXT3_TOPOEXT
> > > feature is supported. This is required to support hyperthreading
> > > feature on AMD CPUS. These are supported via CPUID_8000_001E
> > extended
> > > functions.
> > >
> > > Signed-off-by: Stanislav Lanci <pixo@polepetko.eu>
> > > Signed-off-by: Babu Moger <babu.moger@amd.com>
> > > ---
> > > target/i386/cpu.c | 8 ++++++++
> > > 1 file changed, 8 insertions(+)
> > >
> > > diff --git a/target/i386/cpu.c b/target/i386/cpu.c
> > > index a5a480e..191e850 100644
> > > --- a/target/i386/cpu.c
> > > +++ b/target/i386/cpu.c
> > > @@ -3666,6 +3666,14 @@ void cpu_x86_cpuid(CPUX86State *env,
> > uint32_t index, uint32_t count,
> > > *edx = 0;
> > > }
> > > break;
> > > + case 0x8000001E:
> > > + if (env->features[FEAT_8000_0001_ECX] & CPUID_EXT3_TOPOEXT) {
> > > + *eax = cpu->apic_id;
> > > + *ebx = (cs->nr_threads - 1) << 8 | cpu->core_id;
> >
> > Do we somewhere assert that AMD cannot have cpu->core_id > 255?
> > (qemu does allow weird configurations.)
>
> I don't see specific assert on core_id. But, I see that qemu does not allow nr_cores more than 255.
> Also I see that core_id is iterated based on nr_cores. If you strongly believe we need to add assert here, I will add it.
> Let me know.
A user can emulate AMD with x2apic and intel-iommu to allow more than
255 vcpus and all of them can be a separate core (or its own socket),
which would overflow this (or the next counter).
Forbidding that crazy configuration may be preferable, but an assert
won't hurt now,
thanks.
> > Thanks.
> >
> > > + *ecx = cpu->socket_id;
> > > + *edx = 0;
> > > + }
> > > + break;
> > > case 0xC0000000:
> > > *eax = env->cpuid_xlevel2;
> > > *ebx = 0;
> > > --
> > > 1.8.3.1
> > >
WARNING: multiple messages have this Message-ID (diff)
From: "Radim Krčmář" <rkrcmar@redhat.com>
To: "Moger, Babu" <Babu.Moger@amd.com>
Cc: "pbonzini@redhat.com" <pbonzini@redhat.com>,
"rth@twiddle.net" <rth@twiddle.net>,
"ehabkost@redhat.com" <ehabkost@redhat.com>,
"mtosatti@redhat.com" <mtosatti@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"pixo@polepetko.eu" <pixo@polepetko.eu>,
"Hook, Gary" <Gary.Hook@amd.com>
Subject: Re: [Qemu-devel] [PATCH v2 3/5] target/i386: Add support for CPUID_8000_001E for AMD
Date: Thu, 1 Mar 2018 20:57:16 +0100 [thread overview]
Message-ID: <20180301195715.GA28948@flask> (raw)
In-Reply-To: <CY4PR12MB1768464C5ABB828EEA45166B95C70@CY4PR12MB1768.namprd12.prod.outlook.com>
2018-02-28 22:18+0000, Moger, Babu:
> > -----Original Message-----
> > From: Radim Krčmář [mailto:rkrcmar@redhat.com]
> > Sent: Wednesday, February 28, 2018 12:24 PM
> > To: Moger, Babu <Babu.Moger@amd.com>
> > Cc: pbonzini@redhat.com; rth@twiddle.net; ehabkost@redhat.com;
> > mtosatti@redhat.com; qemu-devel@nongnu.org; kvm@vger.kernel.org;
> > pixo@polepetko.eu; Hook, Gary <Gary.Hook@amd.com>
> > Subject: Re: [PATCH v2 3/5] target/i386: Add support for CPUID_8000_001E
> > for AMD
> >
> > 2018-02-23 21:30-0500, Babu Moger:
> > > From: Stanislav Lanci <pixo@polepetko.eu>
> > >
> > > Populate threads/core_id/apic_ids/socket_id when CPUID_EXT3_TOPOEXT
> > > feature is supported. This is required to support hyperthreading
> > > feature on AMD CPUS. These are supported via CPUID_8000_001E
> > extended
> > > functions.
> > >
> > > Signed-off-by: Stanislav Lanci <pixo@polepetko.eu>
> > > Signed-off-by: Babu Moger <babu.moger@amd.com>
> > > ---
> > > target/i386/cpu.c | 8 ++++++++
> > > 1 file changed, 8 insertions(+)
> > >
> > > diff --git a/target/i386/cpu.c b/target/i386/cpu.c
> > > index a5a480e..191e850 100644
> > > --- a/target/i386/cpu.c
> > > +++ b/target/i386/cpu.c
> > > @@ -3666,6 +3666,14 @@ void cpu_x86_cpuid(CPUX86State *env,
> > uint32_t index, uint32_t count,
> > > *edx = 0;
> > > }
> > > break;
> > > + case 0x8000001E:
> > > + if (env->features[FEAT_8000_0001_ECX] & CPUID_EXT3_TOPOEXT) {
> > > + *eax = cpu->apic_id;
> > > + *ebx = (cs->nr_threads - 1) << 8 | cpu->core_id;
> >
> > Do we somewhere assert that AMD cannot have cpu->core_id > 255?
> > (qemu does allow weird configurations.)
>
> I don't see specific assert on core_id. But, I see that qemu does not allow nr_cores more than 255.
> Also I see that core_id is iterated based on nr_cores. If you strongly believe we need to add assert here, I will add it.
> Let me know.
A user can emulate AMD with x2apic and intel-iommu to allow more than
255 vcpus and all of them can be a separate core (or its own socket),
which would overflow this (or the next counter).
Forbidding that crazy configuration may be preferable, but an assert
won't hurt now,
thanks.
> > Thanks.
> >
> > > + *ecx = cpu->socket_id;
> > > + *edx = 0;
> > > + }
> > > + break;
> > > case 0xC0000000:
> > > *eax = env->cpuid_xlevel2;
> > > *ebx = 0;
> > > --
> > > 1.8.3.1
> > >
next prev parent reply other threads:[~2018-03-01 19:57 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-24 2:30 [PATCH v2 0/5] Enable TOPOEXT to support hyperthreading on AMD CPU Babu Moger
2018-02-24 2:30 ` [Qemu-devel] " Babu Moger
2018-02-24 2:30 ` [PATCH v2 1/5] target/i386: Fix a minor typo found while reviwing Babu Moger
2018-02-24 2:30 ` [Qemu-devel] " Babu Moger
2018-02-28 17:38 ` Radim Krčmář
2018-02-28 17:38 ` [Qemu-devel] " Radim Krčmář
2018-02-28 18:49 ` Eric Blake
2018-02-28 18:49 ` [Qemu-devel] " Eric Blake
2018-02-28 21:20 ` Moger, Babu
2018-02-28 21:20 ` [Qemu-devel] " Moger, Babu
2018-02-28 21:12 ` Moger, Babu
2018-02-28 21:12 ` [Qemu-devel] " Moger, Babu
2018-02-24 2:30 ` [PATCH v2 2/5] target/i386: Populate AMD Processor Cache Information Babu Moger
2018-02-24 2:30 ` [Qemu-devel] " Babu Moger
2018-02-28 18:08 ` Radim Krčmář
2018-02-28 18:08 ` [Qemu-devel] " Radim Krčmář
2018-03-01 15:55 ` Moger, Babu
2018-03-01 15:55 ` [Qemu-devel] " Moger, Babu
2018-03-01 19:56 ` Radim Krčmář
2018-03-01 19:56 ` [Qemu-devel] " Radim Krčmář
2018-03-02 16:50 ` Moger, Babu
2018-03-02 16:50 ` [Qemu-devel] " Moger, Babu
2018-02-24 2:30 ` [PATCH v2 3/5] target/i386: Add support for CPUID_8000_001E for AMD Babu Moger
2018-02-24 2:30 ` [Qemu-devel] " Babu Moger
2018-02-28 18:24 ` Radim Krčmář
2018-02-28 18:24 ` [Qemu-devel] " Radim Krčmář
2018-02-28 22:18 ` Moger, Babu
2018-02-28 22:18 ` [Qemu-devel] " Moger, Babu
2018-03-01 19:57 ` Radim Krčmář [this message]
2018-03-01 19:57 ` Radim Krčmář
2018-03-02 16:50 ` Moger, Babu
2018-03-02 16:50 ` [Qemu-devel] " Moger, Babu
2018-02-24 2:30 ` [PATCH v2 4/5] target/i386: Enable TOPOEXT feature on AMD EPYC CPU Babu Moger
2018-02-24 2:30 ` [Qemu-devel] " Babu Moger
2018-02-24 2:30 ` [PATCH v2 5/5] target/i386: Remove generic SMT thread check Babu Moger
2018-02-24 2:30 ` [Qemu-devel] " Babu Moger
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=20180301195715.GA28948@flask \
--to=rkrcmar@redhat.com \
--cc=Babu.Moger@amd.com \
--cc=Gary.Hook@amd.com \
--cc=ehabkost@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--cc=pixo@polepetko.eu \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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.