From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eduardo Habkost Subject: Re: [PATCH v7 7/9] i386: Add support for CPUID_8000_001E for AMD Date: Fri, 11 May 2018 11:12:01 -0300 Message-ID: <20180511141201.GK25013@localhost.localdomain> References: <1524760009-24710-1-git-send-email-babu.moger@amd.com> <1524760009-24710-8-git-send-email-babu.moger@amd.com> <20180507193944.GF13350@localhost.localdomain> <20180508141632.GJ25013@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: "geoff@hostfission.com" , "kvm@vger.kernel.org" , "mst@redhat.com" , "kash@tripleback.net" , "mtosatti@redhat.com" , "qemu-devel@nongnu.org" , "marcel@redhat.com" , "pbonzini@redhat.com" , "rth@twiddle.net" To: "Moger, Babu" Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: qemu-devel-bounces+gceq-qemu-devel2=m.gmane.org@nongnu.org Sender: "Qemu-devel" List-Id: kvm.vger.kernel.org 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 > > 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. -- Eduardo