Re: [PATCH RFC 1/1] KVM: PPC: Book3S HV: pack VCORE IDs to access full VCPU ID space

2018-05-02 Thread Sam Bobroff
On Thu, May 03, 2018 at 01:11:13PM +1000, David Gibson wrote: > On Tue, May 01, 2018 at 02:52:21PM +1000, Sam Bobroff wrote: > > On Tue, Apr 24, 2018 at 01:48:25PM +1000, David Gibson wrote: > > > On Tue, Apr 24, 2018 at 01:19:15PM +1000, Sam Bobroff wrote: > > > > On Mon, Apr 23, 2018 at 11:06:35A

Re: [PATCH RFC 1/1] KVM: PPC: Book3S HV: pack VCORE IDs to access full VCPU ID space

2018-05-02 Thread David Gibson
On Tue, May 01, 2018 at 02:52:21PM +1000, Sam Bobroff wrote: > On Tue, Apr 24, 2018 at 01:48:25PM +1000, David Gibson wrote: > > On Tue, Apr 24, 2018 at 01:19:15PM +1000, Sam Bobroff wrote: > > > On Mon, Apr 23, 2018 at 11:06:35AM +0200, Cédric Le Goater wrote: > > > > On 04/16/2018 06:09 AM, David

Re: [PATCH RFC 1/1] KVM: PPC: Book3S HV: pack VCORE IDs to access full VCPU ID space

2018-04-30 Thread Sam Bobroff
On Tue, Apr 24, 2018 at 01:48:25PM +1000, David Gibson wrote: > On Tue, Apr 24, 2018 at 01:19:15PM +1000, Sam Bobroff wrote: > > On Mon, Apr 23, 2018 at 11:06:35AM +0200, Cédric Le Goater wrote: > > > On 04/16/2018 06:09 AM, David Gibson wrote: > > > > On Thu, Apr 12, 2018 at 05:02:06PM +1000, Sam

Re: [PATCH RFC 1/1] KVM: PPC: Book3S HV: pack VCORE IDs to access full VCPU ID space

2018-04-24 Thread Cédric Le Goater
On 04/24/2018 05:19 AM, Sam Bobroff wrote: > On Mon, Apr 23, 2018 at 11:06:35AM +0200, Cédric Le Goater wrote: >> On 04/16/2018 06:09 AM, David Gibson wrote: >>> On Thu, Apr 12, 2018 at 05:02:06PM +1000, Sam Bobroff wrote: It is not currently possible to create the full number of possible

Re: [PATCH RFC 1/1] KVM: PPC: Book3S HV: pack VCORE IDs to access full VCPU ID space

2018-04-23 Thread David Gibson
On Tue, Apr 24, 2018 at 01:19:15PM +1000, Sam Bobroff wrote: > On Mon, Apr 23, 2018 at 11:06:35AM +0200, Cédric Le Goater wrote: > > On 04/16/2018 06:09 AM, David Gibson wrote: > > > On Thu, Apr 12, 2018 at 05:02:06PM +1000, Sam Bobroff wrote: > > >> It is not currently possible to create the full

Re: [PATCH RFC 1/1] KVM: PPC: Book3S HV: pack VCORE IDs to access full VCPU ID space

2018-04-23 Thread Sam Bobroff
On Mon, Apr 23, 2018 at 11:06:35AM +0200, Cédric Le Goater wrote: > On 04/16/2018 06:09 AM, David Gibson wrote: > > On Thu, Apr 12, 2018 at 05:02:06PM +1000, Sam Bobroff wrote: > >> It is not currently possible to create the full number of possible > >> VCPUs (KVM_MAX_VCPUS) on Power9 with KVM-HV w

Re: [PATCH RFC 1/1] KVM: PPC: Book3S HV: pack VCORE IDs to access full VCPU ID space

2018-04-23 Thread Cédric Le Goater
On 04/16/2018 06:09 AM, David Gibson wrote: > On Thu, Apr 12, 2018 at 05:02:06PM +1000, Sam Bobroff wrote: >> It is not currently possible to create the full number of possible >> VCPUs (KVM_MAX_VCPUS) on Power9 with KVM-HV when the guest uses less >> threads per core than it's core stride (or "VSM

Re: [PATCH RFC 1/1] KVM: PPC: Book3S HV: pack VCORE IDs to access full VCPU ID space

2018-04-15 Thread David Gibson
On Thu, Apr 12, 2018 at 05:02:06PM +1000, Sam Bobroff wrote: > It is not currently possible to create the full number of possible > VCPUs (KVM_MAX_VCPUS) on Power9 with KVM-HV when the guest uses less > threads per core than it's core stride (or "VSMT mode"). This is > because the VCORE ID and XIVE

[PATCH RFC 1/1] KVM: PPC: Book3S HV: pack VCORE IDs to access full VCPU ID space

2018-04-12 Thread Sam Bobroff
It is not currently possible to create the full number of possible VCPUs (KVM_MAX_VCPUS) on Power9 with KVM-HV when the guest uses less threads per core than it's core stride (or "VSMT mode"). This is because the VCORE ID and XIVE offsets to grow beyond KVM_MAX_VCPUS even though the VCPU ID is less