From: Eduardo Habkost <ehabkost@redhat.com>
To: "Moger, Babu" <Babu.Moger@amd.com>
Cc: "mst@redhat.com" <mst@redhat.com>,
"marcel@redhat.com" <marcel@redhat.com>,
"pbonzini@redhat.com" <pbonzini@redhat.com>,
"rth@twiddle.net" <rth@twiddle.net>,
"mtosatti@redhat.com" <mtosatti@redhat.com>,
"geoff@hostfission.com" <geoff@hostfission.com>,
"kash@tripleback.net" <kash@tripleback.net>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] [PATCH v7 7/9] i386: Add support for CPUID_8000_001E for AMD
Date: Fri, 11 May 2018 11:59:35 -0300 [thread overview]
Message-ID: <20180511145935.GO25013@localhost.localdomain> (raw)
In-Reply-To: <BL0PR12MB2468AFEB39A2BDF45C8BDCD2959F0@BL0PR12MB2468.namprd12.prod.outlook.com>
On Fri, May 11, 2018 at 02:44:11PM +0000, Moger, Babu wrote:
>
>
> > -----Original Message-----
> > From: Eduardo Habkost [mailto:ehabkost@redhat.com]
> > Sent: Friday, May 11, 2018 9:12 AM
> > To: Moger, Babu <Babu.Moger@amd.com>
> > Cc: mst@redhat.com; marcel@redhat.com; pbonzini@redhat.com;
> > rth@twiddle.net; mtosatti@redhat.com; geoff@hostfission.com;
> > kash@tripleback.net; qemu-devel@nongnu.org; kvm@vger.kernel.org
> > Subject: Re: [Qemu-devel] [PATCH v7 7/9] i386: Add support for
> > CPUID_8000_001E for AMD
> >
> > On Tue, May 08, 2018 at 03:02:07PM +0000, Moger, Babu wrote:
> > >
> > > > -----Original Message-----
> > > > From: Eduardo Habkost [mailto:ehabkost@redhat.com]
> > > > Sent: Tuesday, May 8, 2018 9:17 AM
> > > > To: Moger, Babu <Babu.Moger@amd.com>
> > > > Cc: mst@redhat.com; marcel@redhat.com; pbonzini@redhat.com;
> > > > rth@twiddle.net; mtosatti@redhat.com; geoff@hostfission.com;
> > > > kash@tripleback.net; qemu-devel@nongnu.org; kvm@vger.kernel.org
> > > > Subject: Re: [Qemu-devel] [PATCH v7 7/9] i386: Add support for
> > > > CPUID_8000_001E for AMD
> > > >
> > > > On Mon, May 07, 2018 at 11:44:31PM +0000, Moger, Babu wrote:
> > > > [...]
> > > > > > > +
> > > > > > > /*
> > > > > > > * Encode cache info for CPUID[0x80000006].ECX and
> > > > > > CPUID[0x80000006].EDX
> > > > > > > * @l3 can be NULL.
> > > > > > > @@ -4105,6 +4111,14 @@ void cpu_x86_cpuid(CPUX86State *env,
> > > > > > uint32_t index, uint32_t count,
> > > > > > > break;
> > > > > > > }
> > > > > > > break;
> > > > > > > + case 0x8000001E:
> > > > > > > + assert(cpu->core_id <= 255);
> > > > > >
> > > > > > Where's the code that ensures this assert() line can't be
> > > > > > triggered by any command-line configuration?
> > > > >
> > > > > I did not understand this. Can you please elaborate. Thanks
> > > >
> > > > The user must not be able to trigger an assert(), so we need to
> > > > ensure that core_id will never be larger than 255. Is there
> > > > existing code that ensures that?
> > >
> > > I see that max_cpus is set to 255 and also there are checks to make sure
> > core_id does not go above 255.
> > > I verified it while testing. So, probably we don't need assert here. Radim
> > asked me to add this assert.
> > > I can remove it if no abjections.
> >
> > Sorry for not replying to this before: no objection to the
> > assert(), especially considering it will trigger very early on
> > initialization if we break it one day.
>
> Ok. No problem. I will add it back and send a v9 version.
> Please let me know if you have any other feedback for v8 version(sent yesterday).
Thanks, I just saw v8 on my mailbox. No need to send v9 just
because of the assert(), I can re-add it while committing if
necessary.
--
Eduardo
next prev parent reply other threads:[~2018-05-11 14:59 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-26 16:26 [Qemu-devel] [PATCH v7 0/9] i386: Enable TOPOEXT to support hyperthreading on AMD CPU Babu Moger
2018-04-26 16:26 ` [Qemu-devel] [PATCH v7 1/9] i386: Helpers to encode cache information consistently Babu Moger
2018-05-07 19:05 ` Eduardo Habkost
2018-05-07 21:14 ` Moger, Babu
2018-05-07 21:27 ` Eduardo Habkost
2018-05-07 22:47 ` Moger, Babu
2018-05-08 18:40 ` Moger, Babu
2018-05-08 19:07 ` Eduardo Habkost
2018-05-08 19:34 ` Moger, Babu
2018-04-26 16:26 ` [Qemu-devel] [PATCH v7 2/9] i386: Add cache information in X86CPUDefinition Babu Moger
2018-05-07 19:09 ` Eduardo Habkost
2018-05-07 22:56 ` Moger, Babu
2018-04-26 16:26 ` [Qemu-devel] [PATCH v7 3/9] i386: Initialize cache information for EPYC family processors Babu Moger
2018-05-07 20:22 ` Eduardo Habkost
2018-04-26 16:26 ` [Qemu-devel] [PATCH v7 4/9] i386: Add new property to control cache info Babu Moger
2018-05-07 19:14 ` Eduardo Habkost
2018-05-07 23:29 ` Moger, Babu
2018-05-08 14:25 ` Eduardo Habkost
2018-05-08 17:26 ` Moger, Babu
2018-05-08 18:33 ` Eduardo Habkost
2018-05-08 18:44 ` Moger, Babu
2018-04-26 16:26 ` [Qemu-devel] [PATCH v7 5/9] i386: Use the statically loaded cache definitions Babu Moger
2018-05-07 19:15 ` Eduardo Habkost
2018-05-07 23:32 ` Moger, Babu
2018-05-07 19:37 ` Eduardo Habkost
2018-05-07 23:39 ` Moger, Babu
2018-05-08 14:12 ` Eduardo Habkost
2018-05-08 17:08 ` Moger, Babu
2018-04-26 16:26 ` [Qemu-devel] [PATCH v7 6/9] i386: Populate AMD Processor Cache Information for cpuid 0x8000001D Babu Moger
2018-05-07 21:06 ` Eduardo Habkost
2018-05-08 16:41 ` Moger, Babu
2018-04-26 16:26 ` [Qemu-devel] [PATCH v7 7/9] i386: Add support for CPUID_8000_001E for AMD Babu Moger
2018-05-07 19:39 ` Eduardo Habkost
2018-05-07 23:44 ` Moger, Babu
2018-05-08 14:16 ` Eduardo Habkost
2018-05-08 15:02 ` Moger, Babu
2018-05-11 14:12 ` Eduardo Habkost
2018-05-11 14:44 ` Moger, Babu
2018-05-11 14:59 ` Eduardo Habkost [this message]
2018-04-26 16:26 ` [Qemu-devel] [PATCH v7 8/9] i386: Enable TOPOEXT feature on AMD EPYC CPU Babu Moger
2018-05-07 21:07 ` Eduardo Habkost
2018-04-26 16:26 ` [Qemu-devel] [PATCH v7 9/9] i386: Remove generic SMT thread check Babu Moger
2018-05-07 21:14 ` Eduardo Habkost
2018-04-26 20:49 ` [Qemu-devel] [PATCH v7 0/9] i386: Enable TOPOEXT to support hyperthreading on AMD CPU geoff
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=20180511145935.GO25013@localhost.localdomain \
--to=ehabkost@redhat.com \
--cc=Babu.Moger@amd.com \
--cc=geoff@hostfission.com \
--cc=kash@tripleback.net \
--cc=kvm@vger.kernel.org \
--cc=marcel@redhat.com \
--cc=mst@redhat.com \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--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 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).