VCPU hotplug on KVM/ARM

VCPU hotplug on KVM/ARM

[bthakur]

[-- Attachment #1.1: Type: text/plain, Size: 684 bytes --]

Hi,

 

I hope it is the right forum to post my query.

 

I am currently looking at the possibility of adding a new VCPU to a running
guest VM in KVM/ARM. I see that currently, it is not allowed to add a new
VCPU to a guest VM, if it is already initialized. The first check in
kvm_arch_vcpu_create() returns failure if it is already initialized.

 

There was some work done in QEMU to add support for VCPU hotplug:
https://lists.gnu.org/archive/html/qemu-arm/2017-05/msg00404.html

 

But I am looking at the KVM side for enabling adding a new VCPU. If you can
point me to any relevant work/resources, which I can refer to then it will
help me.

 

Thanks.

 

Regards,

Bhupinder


[-- Attachment #1.2: Type: text/html, Size: 2826 bytes --]

[-- Attachment #2: Type: text/plain, Size: 151 bytes --]

_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm

Re: VCPU hotplug on KVM/ARM

[Christoffer Dall]

Hi Bhupinder,

On Tue, Feb 27, 2018 at 03:01:17PM +0530, bthakur@codeaurora.org wrote:
> I hope it is the right forum to post my query.
> 
>  
> 
> I am currently looking at the possibility of adding a new VCPU to a running
> guest VM in KVM/ARM. I see that currently, it is not allowed to add a new
> VCPU to a guest VM, if it is already initialized. The first check in
> kvm_arch_vcpu_create() returns failure if it is already initialized.
> 

This would require a major rework of a lot of logic surrounding the GIC
and other parts of KVM initialization.

>  
> 
> There was some work done in QEMU to add support for VCPU hotplug:
> https://lists.gnu.org/archive/html/qemu-arm/2017-05/msg00404.html
> 
>  
> 
> But I am looking at the KVM side for enabling adding a new VCPU. If you can
> point me to any relevant work/resources, which I can refer to then it will
> help me.
> 

I don't have any specific pointers, but I was always told that the way
we were going to do CPU hotplug would be to instantiate a large number
of VCPUs, and hotplug would be equivalent to turning on a VCPU which was
previously powered off.

Is this not still a feasible solution?

How does VCPU hotplug work on x86?

Thanks,
-Christoffer

Re: VCPU hotplug on KVM/ARM

[bthakur]

Hi Christoffer,

Thanks for your reply.

On 2018-02-27 16:17, Christoffer Dall wrote:
> Hi Bhupinder,
> 
> On Tue, Feb 27, 2018 at 03:01:17PM +0530, bthakur@codeaurora.org wrote:
>> I hope it is the right forum to post my query.
>> 
>> 
>> 
>> I am currently looking at the possibility of adding a new VCPU to a 
>> running
>> guest VM in KVM/ARM. I see that currently, it is not allowed to add a 
>> new
>> VCPU to a guest VM, if it is already initialized. The first check in
>> kvm_arch_vcpu_create() returns failure if it is already initialized.
>> 
> 
> This would require a major rework of a lot of logic surrounding the GIC
> and other parts of KVM initialization.
> 
>> 
>> 
>> There was some work done in QEMU to add support for VCPU hotplug:
>> https://lists.gnu.org/archive/html/qemu-arm/2017-05/msg00404.html
>> 
>> 
>> 
>> But I am looking at the KVM side for enabling adding a new VCPU. If 
>> you can
>> point me to any relevant work/resources, which I can refer to then it 
>> will
>> help me.
>> 
> 
> I don't have any specific pointers, but I was always told that the way
> we were going to do CPU hotplug would be to instantiate a large number
> of VCPUs, and hotplug would be equivalent to turning on a VCPU which 
> was
> previously powered off.
> 
> Is this not still a feasible solution?
It should be a feasible solution provided the guest VM is not able to 
control the onlining/offlining of VCPUs. It should be controlled by the 
Host.

> 
> How does VCPU hotplug work on x86?
On x86, you can add a vcpu through libvirt setvcpu command and it shows 
up in the guest VM as a new CPU if you do lscpu.

> 
> Thanks,
> -Christoffer

Regards,
Bhupinder

Re: VCPU hotplug on KVM/ARM

[Christoffer Dall]

On Tue, Feb 27, 2018 at 05:34:28PM +0530, bthakur@codeaurora.org wrote:
> Hi Christoffer,
> 
> Thanks for your reply.
> 
> On 2018-02-27 16:17, Christoffer Dall wrote:
> >Hi Bhupinder,
> >
> >On Tue, Feb 27, 2018 at 03:01:17PM +0530, bthakur@codeaurora.org wrote:
> >>I hope it is the right forum to post my query.
> >>
> >>
> >>
> >>I am currently looking at the possibility of adding a new VCPU to a
> >>running
> >>guest VM in KVM/ARM. I see that currently, it is not allowed to add a
> >>new
> >>VCPU to a guest VM, if it is already initialized. The first check in
> >>kvm_arch_vcpu_create() returns failure if it is already initialized.
> >>
> >
> >This would require a major rework of a lot of logic surrounding the GIC
> >and other parts of KVM initialization.
> >
> >>
> >>
> >>There was some work done in QEMU to add support for VCPU hotplug:
> >>https://lists.gnu.org/archive/html/qemu-arm/2017-05/msg00404.html
> >>
> >>
> >>
> >>But I am looking at the KVM side for enabling adding a new VCPU. If you
> >>can
> >>point me to any relevant work/resources, which I can refer to then it
> >>will
> >>help me.
> >>
> >
> >I don't have any specific pointers, but I was always told that the way
> >we were going to do CPU hotplug would be to instantiate a large number
> >of VCPUs, and hotplug would be equivalent to turning on a VCPU which was
> >previously powered off.
> >
> >Is this not still a feasible solution?
> It should be a feasible solution provided the guest VM is not able to
> control the onlining/offlining of VCPUs. It should be controlled by the
> Host.
> 

KVM could simply refuse to turn on some of the CPUs unless given
permission from host userspace.

> >
> >How does VCPU hotplug work on x86?
> On x86, you can add a vcpu through libvirt setvcpu command and it shows up
> in the guest VM as a new CPU if you do lscpu.
> 

Sure, but what is the mechanism, does x86 qemu actually call
KVM_CREATE_VCPU, or is this also a question of turning on already
created vcpus ?

Thanks,
-Christoffer

Re: VCPU hotplug on KVM/ARM

[Andrew Jones]

On Tue, Feb 27, 2018 at 01:46:04PM +0100, Christoffer Dall wrote:
> On Tue, Feb 27, 2018 at 05:34:28PM +0530, bthakur@codeaurora.org wrote:
> > Hi Christoffer,
> > 
> > Thanks for your reply.
> > 
> > On 2018-02-27 16:17, Christoffer Dall wrote:
> > >Hi Bhupinder,
> > >
> > >On Tue, Feb 27, 2018 at 03:01:17PM +0530, bthakur@codeaurora.org wrote:
> > >>I hope it is the right forum to post my query.
> > >>
> > >>
> > >>
> > >>I am currently looking at the possibility of adding a new VCPU to a
> > >>running
> > >>guest VM in KVM/ARM. I see that currently, it is not allowed to add a
> > >>new
> > >>VCPU to a guest VM, if it is already initialized. The first check in
> > >>kvm_arch_vcpu_create() returns failure if it is already initialized.
> > >>
> > >
> > >This would require a major rework of a lot of logic surrounding the GIC
> > >and other parts of KVM initialization.
> > >
> > >>
> > >>
> > >>There was some work done in QEMU to add support for VCPU hotplug:
> > >>https://lists.gnu.org/archive/html/qemu-arm/2017-05/msg00404.html
> > >>
> > >>
> > >>
> > >>But I am looking at the KVM side for enabling adding a new VCPU. If you
> > >>can
> > >>point me to any relevant work/resources, which I can refer to then it
> > >>will
> > >>help me.
> > >>
> > >
> > >I don't have any specific pointers, but I was always told that the way
> > >we were going to do CPU hotplug would be to instantiate a large number
> > >of VCPUs, and hotplug would be equivalent to turning on a VCPU which was
> > >previously powered off.
> > >
> > >Is this not still a feasible solution?
> > It should be a feasible solution provided the guest VM is not able to
> > control the onlining/offlining of VCPUs. It should be controlled by the
> > Host.
> > 
> 
> KVM could simply refuse to turn on some of the CPUs unless given
> permission from host userspace.
> 
> > >
> > >How does VCPU hotplug work on x86?
> > On x86, you can add a vcpu through libvirt setvcpu command and it shows up
> > in the guest VM as a new CPU if you do lscpu.
> > 
> 
> Sure, but what is the mechanism, does x86 qemu actually call
> KVM_CREATE_VCPU, or is this also a question of turning on already
> created vcpus ?
>

CC'ing Igor and qemu-devel

drew

Re: [Qemu-devel] VCPU hotplug on KVM/ARM

[Igor Mammedov]

On Tue, 27 Feb 2018 14:21:31 +0100
Andrew Jones <drjones@redhat.com> wrote:

> On Tue, Feb 27, 2018 at 01:46:04PM +0100, Christoffer Dall wrote:
> > On Tue, Feb 27, 2018 at 05:34:28PM +0530, bthakur@codeaurora.org wrote:  
> > > Hi Christoffer,
> > > 
> > > Thanks for your reply.
> > > 
> > > On 2018-02-27 16:17, Christoffer Dall wrote:  
> > > >Hi Bhupinder,
> > > >
> > > >On Tue, Feb 27, 2018 at 03:01:17PM +0530, bthakur@codeaurora.org wrote:  
> > > >>I hope it is the right forum to post my query.
> > > >>
> > > >>
> > > >>
> > > >>I am currently looking at the possibility of adding a new VCPU to a
> > > >>running
> > > >>guest VM in KVM/ARM. I see that currently, it is not allowed to add a
> > > >>new
> > > >>VCPU to a guest VM, if it is already initialized. The first check in
> > > >>kvm_arch_vcpu_create() returns failure if it is already initialized.
> > > >>  
> > > >
> > > >This would require a major rework of a lot of logic surrounding the GIC
> > > >and other parts of KVM initialization.
> > > >  
> > > >>
> > > >>
> > > >>There was some work done in QEMU to add support for VCPU hotplug:
> > > >>https://lists.gnu.org/archive/html/qemu-arm/2017-05/msg00404.html
> > > >>
> > > >>
> > > >>
> > > >>But I am looking at the KVM side for enabling adding a new VCPU. If you
> > > >>can
> > > >>point me to any relevant work/resources, which I can refer to then it
> > > >>will
> > > >>help me.
> > > >>  
> > > >
> > > >I don't have any specific pointers, but I was always told that the way
> > > >we were going to do CPU hotplug would be to instantiate a large number
> > > >of VCPUs, and hotplug would be equivalent to turning on a VCPU which was
> > > >previously powered off.
> > > >
> > > >Is this not still a feasible solution?  
> > > It should be a feasible solution provided the guest VM is not able to
> > > control the onlining/offlining of VCPUs. It should be controlled by the
> > > Host.
> > >   
> > 
> > KVM could simply refuse to turn on some of the CPUs unless given
> > permission from host userspace.
> >   
> > > >
> > > >How does VCPU hotplug work on x86?  
> > > On x86, you can add a vcpu through libvirt setvcpu command and it shows up
> > > in the guest VM as a new CPU if you do lscpu.
> > >   
> > 
> > Sure, but what is the mechanism, does x86 qemu actually call
> > KVM_CREATE_VCPU, or is this also a question of turning on already
> > created vcpus ?
In QEMU on x86 (and I think ppc, s390 as well), we create vCPUs on demand.

It would be nice if ARM would be able to do that too,
so that it could take advantage of the same code.

 
> CC'ing Igor and qemu-devel
> 
> drew
> 

Re: [Qemu-arm] [Qemu-devel] VCPU hotplug on KVM/ARM

[Peter Maydell]

On 1 March 2018 at 09:50, Igor Mammedov <imammedo@redhat.com> wrote:
> In QEMU on x86 (and I think ppc, s390 as well), we create vCPUs on demand.
>
> It would be nice if ARM would be able to do that too,
> so that it could take advantage of the same code.

It's not clear to me how that would work, given that for
instance the interrupt controller wants to know up-front
how many CPUs it has to deal with.

thanks
-- PMM

Re: [Qemu-devel] [Qemu-arm] VCPU hotplug on KVM/ARM

[David Hildenbrand]

On 01.03.2018 11:05, Peter Maydell wrote:
> On 1 March 2018 at 09:50, Igor Mammedov <imammedo@redhat.com> wrote:
>> In QEMU on x86 (and I think ppc, s390 as well), we create vCPUs on demand.>>
>> It would be nice if ARM would be able to do that too,
>> so that it could take advantage of the same code.
> 
> It's not clear to me how that would work, given that for
> instance the interrupt controller wants to know up-front
> how many CPUs it has to deal with.
>

So how is cpu hotplug handled in HW? Or doesn't it even exist there?

(we have max_cpus for the interrupt controller, but not sure if that is
what we want)

> thanks
> -- PMM
> 
-- 

Thanks,

David / dhildenb

Re: [Qemu-devel] [Qemu-arm] VCPU hotplug on KVM/ARM

[Marc Zyngier]

On 01/03/18 13:32, David Hildenbrand wrote:
> On 01.03.2018 11:05, Peter Maydell wrote:
>> On 1 March 2018 at 09:50, Igor Mammedov <imammedo@redhat.com> wrote:
>>> In QEMU on x86 (and I think ppc, s390 as well), we create vCPUs on demand.>>
>>> It would be nice if ARM would be able to do that too,
>>> so that it could take advantage of the same code.
>>
>> It's not clear to me how that would work, given that for
>> instance the interrupt controller wants to know up-front
>> how many CPUs it has to deal with.
>>
> 
> So how is cpu hotplug handled in HW? Or doesn't it even exist there?

I don't know of any physical system offering that facility.

> (we have max_cpus for the interrupt controller, but not sure if that is
> what we want)
We'd need something along those lines. Each CPU has a notional point to
point link to the interrupt controller (to the redistributor, to be
precise), and this entity must pre-exist.

Thanks,

	M.
-- 
Jazz is not dead. It just smells funny...

Re: VCPU hotplug on KVM/ARM

[Maran Wilson]

It's been a few months since this email thread died off. Has anyone 
started working on a potential solution that would allow VCPU hotplug on 
KVM/ARM ? Or is this a project that is still waiting for an owner who 
has the time and inclination to get started?

Thanks,
-Maran

On 2/27/2018 5:21 AM, Andrew Jones wrote:
> On Tue, Feb 27, 2018 at 01:46:04PM +0100, Christoffer Dall wrote:
>> On Tue, Feb 27, 2018 at 05:34:28PM +0530, bthakur@codeaurora.org wrote:
>>> Hi Christoffer,
>>>
>>> Thanks for your reply.
>>>
>>> On 2018-02-27 16:17, Christoffer Dall wrote:
>>>> Hi Bhupinder,
>>>>
>>>> On Tue, Feb 27, 2018 at 03:01:17PM +0530, bthakur@codeaurora.org wrote:
>>>>> I hope it is the right forum to post my query.
>>>>>
>>>>>
>>>>>
>>>>> I am currently looking at the possibility of adding a new VCPU to a
>>>>> running
>>>>> guest VM in KVM/ARM. I see that currently, it is not allowed to add a
>>>>> new
>>>>> VCPU to a guest VM, if it is already initialized. The first check in
>>>>> kvm_arch_vcpu_create() returns failure if it is already initialized.
>>>>>
>>>> This would require a major rework of a lot of logic surrounding the GIC
>>>> and other parts of KVM initialization.
>>>>
>>>>>
>>>>> There was some work done in QEMU to add support for VCPU hotplug:
>>>>> https://lists.gnu.org/archive/html/qemu-arm/2017-05/msg00404.html
>>>>>
>>>>>
>>>>>
>>>>> But I am looking at the KVM side for enabling adding a new VCPU. If you
>>>>> can
>>>>> point me to any relevant work/resources, which I can refer to then it
>>>>> will
>>>>> help me.
>>>>>
>>>> I don't have any specific pointers, but I was always told that the way
>>>> we were going to do CPU hotplug would be to instantiate a large number
>>>> of VCPUs, and hotplug would be equivalent to turning on a VCPU which was
>>>> previously powered off.
>>>>
>>>> Is this not still a feasible solution?
>>> It should be a feasible solution provided the guest VM is not able to
>>> control the onlining/offlining of VCPUs. It should be controlled by the
>>> Host.
>>>
>> KVM could simply refuse to turn on some of the CPUs unless given
>> permission from host userspace.
>>
>>>> How does VCPU hotplug work on x86?
>>> On x86, you can add a vcpu through libvirt setvcpu command and it shows up
>>> in the guest VM as a new CPU if you do lscpu.
>>>
>> Sure, but what is the mechanism, does x86 qemu actually call
>> KVM_CREATE_VCPU, or is this also a question of turning on already
>> created vcpus ?
>>
> CC'ing Igor and qemu-devel
>
> drew
> _______________________________________________
> kvmarm mailing list
> kvmarm@lists.cs.columbia.edu
> https://lists.cs.columbia.edu/mailman/listinfo/kvmarm

Re: [Qemu-devel] VCPU hotplug on KVM/ARM

[Igor Mammedov]

On Tue, 24 Jul 2018 11:35:31 -0700
Maran Wilson <maran.wilson@oracle.com> wrote:

> It's been a few months since this email thread died off. Has anyone 
> started working on a potential solution that would allow VCPU hotplug on 
> KVM/ARM ? Or is this a project that is still waiting for an owner who 
> has the time and inclination to get started?
I'm working on QEMU side of it as time allows.

I can guide or share task if are you interested in helping out with it?


> Thanks,
> -Maran
> 
> On 2/27/2018 5:21 AM, Andrew Jones wrote:
> > On Tue, Feb 27, 2018 at 01:46:04PM +0100, Christoffer Dall wrote:  
> >> On Tue, Feb 27, 2018 at 05:34:28PM +0530, bthakur@codeaurora.org wrote:  
> >>> Hi Christoffer,
> >>>
> >>> Thanks for your reply.
> >>>
> >>> On 2018-02-27 16:17, Christoffer Dall wrote:  
> >>>> Hi Bhupinder,
> >>>>
> >>>> On Tue, Feb 27, 2018 at 03:01:17PM +0530, bthakur@codeaurora.org wrote:  
> >>>>> I hope it is the right forum to post my query.
> >>>>>
> >>>>>
> >>>>>
> >>>>> I am currently looking at the possibility of adding a new VCPU to a
> >>>>> running
> >>>>> guest VM in KVM/ARM. I see that currently, it is not allowed to add a
> >>>>> new
> >>>>> VCPU to a guest VM, if it is already initialized. The first check in
> >>>>> kvm_arch_vcpu_create() returns failure if it is already initialized.
> >>>>>  
> >>>> This would require a major rework of a lot of logic surrounding the GIC
> >>>> and other parts of KVM initialization.
> >>>>  
> >>>>>
> >>>>> There was some work done in QEMU to add support for VCPU hotplug:
> >>>>> https://lists.gnu.org/archive/html/qemu-arm/2017-05/msg00404.html
> >>>>>
> >>>>>
> >>>>>
> >>>>> But I am looking at the KVM side for enabling adding a new VCPU. If you
> >>>>> can
> >>>>> point me to any relevant work/resources, which I can refer to then it
> >>>>> will
> >>>>> help me.
> >>>>>  
> >>>> I don't have any specific pointers, but I was always told that the way
> >>>> we were going to do CPU hotplug would be to instantiate a large number
> >>>> of VCPUs, and hotplug would be equivalent to turning on a VCPU which was
> >>>> previously powered off.
> >>>>
> >>>> Is this not still a feasible solution?  
> >>> It should be a feasible solution provided the guest VM is not able to
> >>> control the onlining/offlining of VCPUs. It should be controlled by the
> >>> Host.
> >>>  
> >> KVM could simply refuse to turn on some of the CPUs unless given
> >> permission from host userspace.
> >>  
> >>>> How does VCPU hotplug work on x86?  
> >>> On x86, you can add a vcpu through libvirt setvcpu command and it shows up
> >>> in the guest VM as a new CPU if you do lscpu.
> >>>  
> >> Sure, but what is the mechanism, does x86 qemu actually call
> >> KVM_CREATE_VCPU, or is this also a question of turning on already
> >> created vcpus ?
> >>  
> > CC'ing Igor and qemu-devel
> >
> > drew
> > _______________________________________________
> > kvmarm mailing list
> > kvmarm@lists.cs.columbia.edu
> > https://lists.cs.columbia.edu/mailman/listinfo/kvmarm  
> 
> 

Re: VCPU hotplug on KVM/ARM

[Marc Zyngier]

On 24/07/18 19:35, Maran Wilson wrote:
> It's been a few months since this email thread died off. Has anyone 
> started working on a potential solution that would allow VCPU hotplug on 
> KVM/ARM ? Or is this a project that is still waiting for an owner who 
> has the time and inclination to get started?

This is typically a project for someone who would have this particular
itch to scratch, and who has a demonstrable need for this functionality.

Work wise, it would have to include adding physical CPU hotplug support
to the arm64 kernel as a precondition, before worrying about doing it in
KVM.

For KVM itself, particular area of interests would be:
- Making GICv3 redistributors magically appear in the IPA space
- Live resizing of GICv3 structures
- Dynamic allocation of MPIDR, and mapping with vcpu_id

This should keep someone busy for a good couple of weeks (give or take a
few months).

That being said, I'd rather see support in QEMU first, creating all the
vcpu/redistributors upfront, and signalling the hotplug event via the
virtual firmware. And then post some numbers to show that creating all
the vcpus upfront is not acceptable.

Thanks,

	M.
-- 
Jazz is not dead. It just smells funny...

Re: [Qemu-devel] VCPU hotplug on KVM/ARM

[Andrew Jones]

On Wed, Jul 25, 2018 at 11:40:54AM +0100, Marc Zyngier wrote:
> On 24/07/18 19:35, Maran Wilson wrote:
> > It's been a few months since this email thread died off. Has anyone 
> > started working on a potential solution that would allow VCPU hotplug on 
> > KVM/ARM ? Or is this a project that is still waiting for an owner who 
> > has the time and inclination to get started?
> 
> This is typically a project for someone who would have this particular
> itch to scratch, and who has a demonstrable need for this functionality.
> 
> Work wise, it would have to include adding physical CPU hotplug support
> to the arm64 kernel as a precondition, before worrying about doing it in
> KVM.
> 
> For KVM itself, particular area of interests would be:
> - Making GICv3 redistributors magically appear in the IPA space
> - Live resizing of GICv3 structures
> - Dynamic allocation of MPIDR, and mapping with vcpu_id

I have CPU topology description patches on the QEMU list now[*]. A next
step for me is to this MPIDR work. I probably won't get to it until the
end of August though.

[*] http://lists.nongnu.org/archive/html/qemu-devel/2018-07/msg01168.html

> 
> This should keep someone busy for a good couple of weeks (give or take a
> few months).

:-)

> 
> That being said, I'd rather see support in QEMU first, creating all the
> vcpu/redistributors upfront, and signalling the hotplug event via the
> virtual firmware. And then post some numbers to show that creating all
> the vcpus upfront is not acceptable.

I think the upfront allocation, allocating all possible cpus, but only
activating all present cpus, was the planned approach. What were the
concerns about that approach? Just vcpu memory overhead for too many
overly ambitious VM configs?

Thanks,
drew

Re: [Qemu-devel] VCPU hotplug on KVM/ARM

[Marc Zyngier]

On 25/07/18 13:28, Andrew Jones wrote:
> On Wed, Jul 25, 2018 at 11:40:54AM +0100, Marc Zyngier wrote:
>> On 24/07/18 19:35, Maran Wilson wrote:
>>> It's been a few months since this email thread died off. Has anyone 
>>> started working on a potential solution that would allow VCPU hotplug on 
>>> KVM/ARM ? Or is this a project that is still waiting for an owner who 
>>> has the time and inclination to get started?
>>
>> This is typically a project for someone who would have this particular
>> itch to scratch, and who has a demonstrable need for this functionality.
>>
>> Work wise, it would have to include adding physical CPU hotplug support
>> to the arm64 kernel as a precondition, before worrying about doing it in
>> KVM.
>>
>> For KVM itself, particular area of interests would be:
>> - Making GICv3 redistributors magically appear in the IPA space
>> - Live resizing of GICv3 structures
>> - Dynamic allocation of MPIDR, and mapping with vcpu_id
> 
> I have CPU topology description patches on the QEMU list now[*]. A next
> step for me is to this MPIDR work. I probably won't get to it until the
> end of August though.
> 
> [*] http://lists.nongnu.org/archive/html/qemu-devel/2018-07/msg01168.html
> 
>>
>> This should keep someone busy for a good couple of weeks (give or take a
>> few months).
> 
> :-)
> 
>>
>> That being said, I'd rather see support in QEMU first, creating all the
>> vcpu/redistributors upfront, and signalling the hotplug event via the
>> virtual firmware. And then post some numbers to show that creating all
>> the vcpus upfront is not acceptable.
> 
> I think the upfront allocation, allocating all possible cpus, but only
> activating all present cpus, was the planned approach. What were the
> concerns about that approach? Just vcpu memory overhead for too many
> overly ambitious VM configs?

I don't have any ARM-specific concern about that, and I think this is
the right approach. It has the good property of not requiring much
change in the kernel (other than actually supporting CPU hotplug).

vcpu memory overhead is a generic concern though, and not only for ARM.
We currently allow up to 512 vcpus per VM, which looks like a lot, but
really isn't. If we're to allow this to be bumped up significantly, we
should start accounting the vcpu-related memory against the user's
allowance...

Thanks,

	M.
-- 
Jazz is not dead. It just smells funny...

Re: [Qemu-devel] VCPU hotplug on KVM/ARM

[Maran Wilson]

Thanks everyone. It sounds like there is consensus around how best to 
proceed (at a high level at least).

Since Igor has already gotten started, I'll coordinate with him offline 
to see where I can jump in.

Thanks,
-Maran

On 7/25/2018 6:07 AM, Marc Zyngier wrote:
> On 25/07/18 13:28, Andrew Jones wrote:
>> On Wed, Jul 25, 2018 at 11:40:54AM +0100, Marc Zyngier wrote:
>>> On 24/07/18 19:35, Maran Wilson wrote:
>>>> It's been a few months since this email thread died off. Has anyone
>>>> started working on a potential solution that would allow VCPU hotplug on
>>>> KVM/ARM ? Or is this a project that is still waiting for an owner who
>>>> has the time and inclination to get started?
>>> This is typically a project for someone who would have this particular
>>> itch to scratch, and who has a demonstrable need for this functionality.
>>>
>>> Work wise, it would have to include adding physical CPU hotplug support
>>> to the arm64 kernel as a precondition, before worrying about doing it in
>>> KVM.
>>>
>>> For KVM itself, particular area of interests would be:
>>> - Making GICv3 redistributors magically appear in the IPA space
>>> - Live resizing of GICv3 structures
>>> - Dynamic allocation of MPIDR, and mapping with vcpu_id
>> I have CPU topology description patches on the QEMU list now[*]. A next
>> step for me is to this MPIDR work. I probably won't get to it until the
>> end of August though.
>>
>> [*] http://lists.nongnu.org/archive/html/qemu-devel/2018-07/msg01168.html
>>
>>> This should keep someone busy for a good couple of weeks (give or take a
>>> few months).
>> :-)
>>
>>> That being said, I'd rather see support in QEMU first, creating all the
>>> vcpu/redistributors upfront, and signalling the hotplug event via the
>>> virtual firmware. And then post some numbers to show that creating all
>>> the vcpus upfront is not acceptable.
>> I think the upfront allocation, allocating all possible cpus, but only
>> activating all present cpus, was the planned approach. What were the
>> concerns about that approach? Just vcpu memory overhead for too many
>> overly ambitious VM configs?
> I don't have any ARM-specific concern about that, and I think this is
> the right approach. It has the good property of not requiring much
> change in the kernel (other than actually supporting CPU hotplug).
>
> vcpu memory overhead is a generic concern though, and not only for ARM.
> We currently allow up to 512 vcpus per VM, which looks like a lot, but
> really isn't. If we're to allow this to be bumped up significantly, we
> should start accounting the vcpu-related memory against the user's
> allowance...
>
> Thanks,
>
> 	M.

Re: [Qemu-devel] VCPU hotplug on KVM/ARM

[Igor Mammedov]

On Wed, 25 Jul 2018 14:07:12 +0100
Marc Zyngier <marc.zyngier@arm.com> wrote:

> On 25/07/18 13:28, Andrew Jones wrote:
> > On Wed, Jul 25, 2018 at 11:40:54AM +0100, Marc Zyngier wrote:  
> >> On 24/07/18 19:35, Maran Wilson wrote:  
> >>> It's been a few months since this email thread died off. Has anyone 
> >>> started working on a potential solution that would allow VCPU hotplug on 
> >>> KVM/ARM ? Or is this a project that is still waiting for an owner who 
> >>> has the time and inclination to get started?  
> >>
> >> This is typically a project for someone who would have this particular
> >> itch to scratch, and who has a demonstrable need for this functionality.
> >>
> >> Work wise, it would have to include adding physical CPU hotplug support
> >> to the arm64 kernel as a precondition, before worrying about doing it in
> >> KVM.
> >>
> >> For KVM itself, particular area of interests would be:
> >> - Making GICv3 redistributors magically appear in the IPA space
> >> - Live resizing of GICv3 structures
> >> - Dynamic allocation of MPIDR, and mapping with vcpu_id  
> > 
> > I have CPU topology description patches on the QEMU list now[*]. A next
> > step for me is to this MPIDR work. I probably won't get to it until the
> > end of August though.
> > 
> > [*] http://lists.nongnu.org/archive/html/qemu-devel/2018-07/msg01168.html
> >   
> >>
> >> This should keep someone busy for a good couple of weeks (give or take a
> >> few months).  
> > 
> > :-)
> >   
> >>
> >> That being said, I'd rather see support in QEMU first, creating all the
> >> vcpu/redistributors upfront, and signalling the hotplug event via the
> >> virtual firmware. And then post some numbers to show that creating all
> >> the vcpus upfront is not acceptable.  
> > 
> > I think the upfront allocation, allocating all possible cpus, but only
> > activating all present cpus, was the planned approach. What were the
> > concerns about that approach? Just vcpu memory overhead for too many
> > overly ambitious VM configs?  
> 
> I don't have any ARM-specific concern about that, and I think this is
> the right approach. It has the good property of not requiring much
> change in the kernel (other than actually supporting CPU hotplug).
for x86 we allocate VCPUs dynamically (both QEMU and KVM)
CCing ppc/s390 folks as I don't recall how it's implemented there.

but we do not delete vcpus in KVM after they were created
(as it deemed to be too complicated), we are just deleting QEMU part
of it and keep kvm's vcpu for reuse with future hotplug.

> vcpu memory overhead is a generic concern though, and not only for ARM.
> We currently allow up to 512 vcpus per VM, which looks like a lot, but
> really isn't. If we're to allow this to be bumped up significantly, we
> should start accounting the vcpu-related memory against the user's
> allowance...
> 
> Thanks,
> 
> 	M.

Re: [Qemu-devel] VCPU hotplug on KVM/ARM

[David Hildenbrand]

On 31.07.2018 12:27, Igor Mammedov wrote:
> On Wed, 25 Jul 2018 14:07:12 +0100
> Marc Zyngier <marc.zyngier@arm.com> wrote:
> 
>> On 25/07/18 13:28, Andrew Jones wrote:
>>> On Wed, Jul 25, 2018 at 11:40:54AM +0100, Marc Zyngier wrote:  
>>>> On 24/07/18 19:35, Maran Wilson wrote:  
>>>>> It's been a few months since this email thread died off. Has anyone 
>>>>> started working on a potential solution that would allow VCPU hotplug on 
>>>>> KVM/ARM ? Or is this a project that is still waiting for an owner who 
>>>>> has the time and inclination to get started?  
>>>>
>>>> This is typically a project for someone who would have this particular
>>>> itch to scratch, and who has a demonstrable need for this functionality.
>>>>
>>>> Work wise, it would have to include adding physical CPU hotplug support
>>>> to the arm64 kernel as a precondition, before worrying about doing it in
>>>> KVM.
>>>>
>>>> For KVM itself, particular area of interests would be:
>>>> - Making GICv3 redistributors magically appear in the IPA space
>>>> - Live resizing of GICv3 structures
>>>> - Dynamic allocation of MPIDR, and mapping with vcpu_id  
>>>
>>> I have CPU topology description patches on the QEMU list now[*]. A next
>>> step for me is to this MPIDR work. I probably won't get to it until the
>>> end of August though.
>>>
>>> [*] http://lists.nongnu.org/archive/html/qemu-devel/2018-07/msg01168.html
>>>   
>>>>
>>>> This should keep someone busy for a good couple of weeks (give or take a
>>>> few months).  
>>>
>>> :-)
>>>   
>>>>
>>>> That being said, I'd rather see support in QEMU first, creating all the
>>>> vcpu/redistributors upfront, and signalling the hotplug event via the
>>>> virtual firmware. And then post some numbers to show that creating all
>>>> the vcpus upfront is not acceptable.  
>>>
>>> I think the upfront allocation, allocating all possible cpus, but only
>>> activating all present cpus, was the planned approach. What were the
>>> concerns about that approach? Just vcpu memory overhead for too many
>>> overly ambitious VM configs?  
>>
>> I don't have any ARM-specific concern about that, and I think this is
>> the right approach. It has the good property of not requiring much
>> change in the kernel (other than actually supporting CPU hotplug).
> for x86 we allocate VCPUs dynamically (both QEMU and KVM)
> CCing ppc/s390 folks as I don't recall how it's implemented there.

s390x: also handled that way. Dynamically allocated.

Unplug: not supported by the architecture and fenced.

I remember a discussion where people said dynamically creating/deleting
VCPUs (and therefore threads) is preferred, because then there is no way
on earth a malicious guest could make use of such a CPU (in case there
would be a subtle BUG in QEMU).

-- 

Thanks,

David / dhildenb

Re: VCPU hotplug on KVM/ARM

[Bharata B Rao]

On Tue, Jul 31, 2018 at 3:57 PM, Igor Mammedov <imammedo@redhat.com> wrote:

> On Wed, 25 Jul 2018 14:07:12 +0100
> Marc Zyngier <marc.zyngier@arm.com> wrote:
>
> > On 25/07/18 13:28, Andrew Jones wrote:
> > > On Wed, Jul 25, 2018 at 11:40:54AM +0100, Marc Zyngier wrote:
> > >> On 24/07/18 19:35, Maran Wilson wrote:
> > >>> It's been a few months since this email thread died off. Has anyone
> > >>> started working on a potential solution that would allow VCPU
> hotplug on
> > >>> KVM/ARM ? Or is this a project that is still waiting for an owner
> who
> > >>> has the time and inclination to get started?
> > >>
> > >> This is typically a project for someone who would have this particular
> > >> itch to scratch, and who has a demonstrable need for this
> functionality.
> > >>
> > >> Work wise, it would have to include adding physical CPU hotplug
> support
> > >> to the arm64 kernel as a precondition, before worrying about doing it
> in
> > >> KVM.
> > >>
> > >> For KVM itself, particular area of interests would be:
> > >> - Making GICv3 redistributors magically appear in the IPA space
> > >> - Live resizing of GICv3 structures
> > >> - Dynamic allocation of MPIDR, and mapping with vcpu_id
> > >
> > > I have CPU topology description patches on the QEMU list now[*]. A next
> > > step for me is to this MPIDR work. I probably won't get to it until the
> > > end of August though.
> > >
> > > [*] http://lists.nongnu.org/archive/html/qemu-devel/2018-
> 07/msg01168.html
> > >
> > >>
> > >> This should keep someone busy for a good couple of weeks (give or
> take a
> > >> few months).
> > >
> > > :-)
> > >
> > >>
> > >> That being said, I'd rather see support in QEMU first, creating all
> the
> > >> vcpu/redistributors upfront, and signalling the hotplug event via the
> > >> virtual firmware. And then post some numbers to show that creating all
> > >> the vcpus upfront is not acceptable.
> > >
> > > I think the upfront allocation, allocating all possible cpus, but only
> > > activating all present cpus, was the planned approach. What were the
> > > concerns about that approach? Just vcpu memory overhead for too many
> > > overly ambitious VM configs?
> >
> > I don't have any ARM-specific concern about that, and I think this is
> > the right approach. It has the good property of not requiring much
> > change in the kernel (other than actually supporting CPU hotplug).
> for x86 we allocate VCPUs dynamically (both QEMU and KVM)
> CCing ppc/s390 folks as I don't recall how it's implemented there.
>
> but we do not delete vcpus in KVM after they were created
> (as it deemed to be too complicated), we are just deleting QEMU part
> of it and keep kvm's vcpu for reuse with future hotplug.
>

Same with PPC, we too dynamically create vcpus and during unplug keep the
KVM's vcpus for reuse.

Regards,
Bharata.