Re: [libvirt] [RFC PATCH 0/2] nodeinfo: PPC64: Fix topology and siblings info on capabilities and nodeinfo

2016-07-21 Thread Daniel P. Berrange
On Thu, Jul 21, 2016 at 05:52:11PM +0200, Andrea Bolognani wrote: > On Wed, 2016-07-20 at 13:49 +0100, Daniel P. Berrange wrote: > > > Additionally, this doesn't tell us anything about whether any > > > host CPU can run a guest CPU: given the above configuration, > > > on ppc64, we know that CPU 1

Re: [libvirt] [RFC PATCH 0/2] nodeinfo: PPC64: Fix topology and siblings info on capabilities and nodeinfo

2016-07-21 Thread Andrea Bolognani
On Wed, 2016-07-20 at 13:49 +0100, Daniel P. Berrange wrote: > > IIRC doing something like this was proposed at some point in > > the past, but was rejected on the ground that existing tools > > assume that 1) CPUs listed in the NUMA topology are online > > and 2) you can pin vCPUs to them. So they

Re: [libvirt] [RFC PATCH 0/2] nodeinfo: PPC64: Fix topology and siblings info on capabilities and nodeinfo

2016-07-20 Thread Daniel P. Berrange
On Wed, Jul 20, 2016 at 02:33:33PM +0200, Andrea Bolognani wrote: > On Tue, 2016-07-19 at 15:35 +0100, Daniel P. Berrange wrote: > > On Thu, May 05, 2016 at 08:48:05PM +0200, Andrea Bolognani wrote: > > >  > > > On Fri, 2016-01-29 at 01:32 -0500, Shivaprasad G Bhat wrote: > > > >  > > > > The nodei

Re: [libvirt] [RFC PATCH 0/2] nodeinfo: PPC64: Fix topology and siblings info on capabilities and nodeinfo

2016-07-20 Thread Andrea Bolognani
On Tue, 2016-07-19 at 15:35 +0100, Daniel P. Berrange wrote: > On Thu, May 05, 2016 at 08:48:05PM +0200, Andrea Bolognani wrote: > >  > > On Fri, 2016-01-29 at 01:32 -0500, Shivaprasad G Bhat wrote: > > >  > > > The nodeinfo output was fixed earlier to reflect the actual cpus > > > available in >

Re: [libvirt] [RFC PATCH 0/2] nodeinfo: PPC64: Fix topology and siblings info on capabilities and nodeinfo

2016-07-19 Thread Daniel P. Berrange
On Thu, May 05, 2016 at 08:48:05PM +0200, Andrea Bolognani wrote: > On Fri, 2016-01-29 at 01:32 -0500, Shivaprasad G Bhat wrote: > > The nodeinfo output was fixed earlier to reflect the actual cpus available > > in > > KVM mode on PPC64. The earlier fixes covered the aspect of not making a host >

Re: [libvirt] [RFC PATCH 0/2] nodeinfo: PPC64: Fix topology and siblings info on capabilities and nodeinfo

2016-06-16 Thread David Gibson
On Fri, 10 Jun 2016 17:52:47 +0200 Andrea Bolognani wrote: > On Tue, 2016-05-31 at 16:08 +1000, David Gibson wrote: > > > QEMU fails with errors like > > >  > > >   qemu-kvm: Cannot support more than 8 threads on PPC with KVM > > >   qemu-kvm: Cannot support more than 1 threads on PPC with TCG >

Re: [libvirt] [RFC PATCH 0/2] nodeinfo: PPC64: Fix topology and siblings info on capabilities and nodeinfo

2016-06-10 Thread Andrea Bolognani
On Tue, 2016-05-31 at 16:08 +1000, David Gibson wrote: > > QEMU fails with errors like > >  > >   qemu-kvm: Cannot support more than 8 threads on PPC with KVM > >   qemu-kvm: Cannot support more than 1 threads on PPC with TCG > >  > > depending on the guest type. >  > Note that in a sense the two e

Re: [libvirt] [RFC PATCH 0/2] nodeinfo: PPC64: Fix topology and siblings info on capabilities and nodeinfo

2016-05-30 Thread David Gibson
On Tue, 17 May 2016 11:49:22 +0200 Andrea Bolognani wrote: > On Tue, 2016-05-10 at 17:59 -0400, Cole Robinson wrote: > > On 05/05/2016 02:48 PM, Andrea Bolognani wrote: > > > On Fri, 2016-01-29 at 01:32 -0500, Shivaprasad G Bhat wrote: > > >  > > > ** Guest threads limit ** > > >  > > > My dual

Re: [libvirt] [RFC PATCH 0/2] nodeinfo: PPC64: Fix topology and siblings info on capabilities and nodeinfo

2016-05-23 Thread Andrea Bolognani
On Thu, 2016-05-05 at 20:48 +0200, Andrea Bolognani wrote: > On Fri, 2016-01-29 at 01:32 -0500, Shivaprasad G Bhat wrote: > > The nodeinfo output was fixed earlier to reflect the actual cpus available > > in > > KVM mode on PPC64. The earlier fixes covered the aspect of not making a host > > look

Re: [libvirt] [RFC PATCH 0/2] nodeinfo: PPC64: Fix topology and siblings info on capabilities and nodeinfo

2016-05-17 Thread Andrea Bolognani
On Tue, 2016-05-10 at 17:59 -0400, Cole Robinson wrote: > On 05/05/2016 02:48 PM, Andrea Bolognani wrote: > > On Fri, 2016-01-29 at 01:32 -0500, Shivaprasad G Bhat wrote: > >  > > ** Guest threads limit ** > >  > > My dual-core laptop will happily run a guest configured with > >  > >    > >  >

Re: [libvirt] [RFC PATCH 0/2] nodeinfo: PPC64: Fix topology and siblings info on capabilities and nodeinfo

2016-05-10 Thread Cole Robinson
On 05/05/2016 02:48 PM, Andrea Bolognani wrote: > On Fri, 2016-01-29 at 01:32 -0500, Shivaprasad G Bhat wrote: >> The nodeinfo output was fixed earlier to reflect the actual cpus available in >> KVM mode on PPC64. The earlier fixes covered the aspect of not making a host >> look overcommitted when

Re: [libvirt] [RFC PATCH 0/2] nodeinfo: PPC64: Fix topology and siblings info on capabilities and nodeinfo

2016-05-05 Thread Andrea Bolognani
On Fri, 2016-01-29 at 01:32 -0500, Shivaprasad G Bhat wrote: > The nodeinfo output was fixed earlier to reflect the actual cpus available in > KVM mode on PPC64. The earlier fixes covered the aspect of not making a host > look overcommitted when its not. The current fixes are aimed at helping the >

Re: [libvirt] [RFC PATCH 0/2] nodeinfo: PPC64: Fix topology and siblings info on capabilities and nodeinfo

2016-02-19 Thread Andrea Bolognani
On Tue, 2016-02-16 at 13:04 +1100, David Gibson wrote: > > So the information don't seem to add up: we claim that the > > host has 160 online CPUs, but the NUMA topology only contains > > information about 5 of them per each node, so 20 in total. > >  > > That's of course because Linux only provide

Re: [libvirt] [RFC PATCH 0/2] nodeinfo: PPC64: Fix topology and siblings info on capabilities and nodeinfo

2016-02-15 Thread David Gibson
On Mon, 08 Feb 2016 20:11:41 +0100 Andrea Bolognani wrote: > On Fri, 2016-01-29 at 01:32 -0500, Shivaprasad G Bhat wrote: > > The nodeinfo output was fixed earlier to reflect the actual cpus available > > in > > KVM mode on PPC64. The earlier fixes covered the aspect of not making a host > > loo

Re: [libvirt] [RFC PATCH 0/2] nodeinfo: PPC64: Fix topology and siblings info on capabilities and nodeinfo

2016-02-08 Thread Andrea Bolognani
On Fri, 2016-01-29 at 01:32 -0500, Shivaprasad G Bhat wrote: > The nodeinfo output was fixed earlier to reflect the actual cpus available in > KVM mode on PPC64. The earlier fixes covered the aspect of not making a host > look overcommitted when its not. The current fixes are aimed at helping the >

[libvirt] [RFC PATCH 0/2] nodeinfo: PPC64: Fix topology and siblings info on capabilities and nodeinfo

2016-01-28 Thread Shivaprasad G Bhat
The nodeinfo output was fixed earlier to reflect the actual cpus available in KVM mode on PPC64. The earlier fixes covered the aspect of not making a host look overcommitted when its not. The current fixes are aimed at helping the users make better decisions on the kind of guest cpu topology that c