Re: [PATCH v5 13/16] target/i386: Add EPYC model specific handlers

2020-03-10 Thread Igor Mammedov
On Mon, 9 Mar 2020 14:12:10 -0500 Babu Moger wrote: > On 3/9/20 10:03 AM, Igor Mammedov wrote: > > On Tue, 03 Mar 2020 13:58:16 -0600 > > Babu Moger wrote: > > > >> Add the new EPYC model specific handlers to fix the apicid decoding. > >> > >> The APIC ID is decoded based on the sequence

Re: [PATCH v5 13/16] target/i386: Add EPYC model specific handlers

2020-03-09 Thread Babu Moger
On 3/9/20 10:03 AM, Igor Mammedov wrote: > On Tue, 03 Mar 2020 13:58:16 -0600 > Babu Moger wrote: > >> Add the new EPYC model specific handlers to fix the apicid decoding. >> >> The APIC ID is decoded based on the sequence sockets->dies->cores->threads. >> This works fine for most standard

Re: [PATCH v5 13/16] target/i386: Add EPYC model specific handlers

2020-03-09 Thread Igor Mammedov
On Tue, 03 Mar 2020 13:58:16 -0600 Babu Moger wrote: > Add the new EPYC model specific handlers to fix the apicid decoding. > > The APIC ID is decoded based on the sequence sockets->dies->cores->threads. > This works fine for most standard AMD and other vendors' configurations, > but this

[PATCH v5 13/16] target/i386: Add EPYC model specific handlers

2020-03-03 Thread Babu Moger
Add the new EPYC model specific handlers to fix the apicid decoding. The APIC ID is decoded based on the sequence sockets->dies->cores->threads. This works fine for most standard AMD and other vendors' configurations, but this decoding sequence does not follow that of AMD's APIC ID enumeration