On Fri, Apr 21, 2017 at 11:38:30AM +0200, Paolo Bonzini wrote:
>
>
> On 20/04/2017 20:42, Eduardo Habkost wrote:
> >> -smp 4,threads=4 shows 4 cores
> > This means 1 socket with 1 core, 4 threads per core. But if
> > vendor ID is AMD, guests will probably ignore the hyperthreading
> > info and tr
On 20/04/2017 20:42, Eduardo Habkost wrote:
>> -smp 4,threads=4 shows 4 cores
> This means 1 socket with 1 core, 4 threads per core. But if
> vendor ID is AMD, guests will probably ignore the hyperthreading
> info and treat each thread as a separate core. That's why we have
> a warning.
I'm not
On Thu, Apr 20, 2017 at 12:14:18AM -0400, Pranith Kumar wrote:
> On Wed, Apr 19, 2017 at 10:26 PM, Eduardo Habkost wrote:
> > On Wed, Apr 19, 2017 at 06:03:01PM -0400, Pranith Kumar wrote:
> >> On Wed, Apr 19, 2017 at 5:33 PM, Eduardo Habkost
> >> wrote:
> >> > On Wed, Apr 19, 2017 at 05:25:23PM
On Wed, Apr 19, 2017 at 10:26 PM, Eduardo Habkost wrote:
> On Wed, Apr 19, 2017 at 06:03:01PM -0400, Pranith Kumar wrote:
>> On Wed, Apr 19, 2017 at 5:33 PM, Eduardo Habkost wrote:
>> > On Wed, Apr 19, 2017 at 05:25:23PM -0400, Pranith Kumar wrote:
>> >> On Wed, Apr 19, 2017 at 4:57 PM, Eduardo H
On Wed, Apr 19, 2017 at 06:03:01PM -0400, Pranith Kumar wrote:
> On Wed, Apr 19, 2017 at 5:33 PM, Eduardo Habkost wrote:
> > On Wed, Apr 19, 2017 at 05:25:23PM -0400, Pranith Kumar wrote:
> >> On Wed, Apr 19, 2017 at 4:57 PM, Eduardo Habkost
> >> wrote:
> >> > On Wed, Apr 19, 2017 at 04:16:53PM
On Wed, Apr 19, 2017 at 5:33 PM, Eduardo Habkost wrote:
> On Wed, Apr 19, 2017 at 05:25:23PM -0400, Pranith Kumar wrote:
>> On Wed, Apr 19, 2017 at 4:57 PM, Eduardo Habkost wrote:
>> > On Wed, Apr 19, 2017 at 04:16:53PM -0400, Pranith Kumar wrote:
>> >> On Wed, Apr 19, 2017 at 4:13 PM, Eduardo Ha
On Wed, Apr 19, 2017 at 05:25:23PM -0400, Pranith Kumar wrote:
> On Wed, Apr 19, 2017 at 4:57 PM, Eduardo Habkost wrote:
> > On Wed, Apr 19, 2017 at 04:16:53PM -0400, Pranith Kumar wrote:
> >> On Wed, Apr 19, 2017 at 4:13 PM, Eduardo Habkost
> >> wrote:
> >> > On Wed, Apr 19, 2017 at 04:00:49PM
On Wed, Apr 19, 2017 at 4:57 PM, Eduardo Habkost wrote:
> On Wed, Apr 19, 2017 at 04:16:53PM -0400, Pranith Kumar wrote:
>> On Wed, Apr 19, 2017 at 4:13 PM, Eduardo Habkost wrote:
>> > On Wed, Apr 19, 2017 at 04:00:49PM -0400, Pranith Kumar wrote:
>> >> On Wed, Apr 19, 2017 at 3:54 PM, Pranith Ku
On Wed, Apr 19, 2017 at 04:16:53PM -0400, Pranith Kumar wrote:
> On Wed, Apr 19, 2017 at 4:13 PM, Eduardo Habkost wrote:
> > On Wed, Apr 19, 2017 at 04:00:49PM -0400, Pranith Kumar wrote:
> >> On Wed, Apr 19, 2017 at 3:54 PM, Pranith Kumar
> >> wrote:
> >> > When we enable hyperthreading (using
On Wed, Apr 19, 2017 at 4:13 PM, Eduardo Habkost wrote:
> On Wed, Apr 19, 2017 at 04:00:49PM -0400, Pranith Kumar wrote:
>> On Wed, Apr 19, 2017 at 3:54 PM, Pranith Kumar wrote:
>> > When we enable hyperthreading (using threads smp argument), we warn
>> > the user if the cpu is an AMD cpu. This d
On Wed, Apr 19, 2017 at 04:00:49PM -0400, Pranith Kumar wrote:
> On Wed, Apr 19, 2017 at 3:54 PM, Pranith Kumar wrote:
> > When we enable hyperthreading (using threads smp argument), we warn
> > the user if the cpu is an AMD cpu. This does not make sense on TCG and
> > is also obsolete now that AM
On Wed, Apr 19, 2017 at 3:54 PM, Pranith Kumar wrote:
> When we enable hyperthreading (using threads smp argument), we warn
> the user if the cpu is an AMD cpu. This does not make sense on TCG and
> is also obsolete now that AMD Ryzen support hyperthreading.
>
> Fix this by adding CPUID_HT bit to
When we enable hyperthreading (using threads smp argument), we warn
the user if the cpu is an AMD cpu. This does not make sense on TCG and
is also obsolete now that AMD Ryzen support hyperthreading.
Fix this by adding CPUID_HT bit to the TCG features and explicitly
checking this bit in the cpuid.
13 matches
Mail list logo