All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoffer Dall <cdall@cs.columbia.edu>
To: bthakur@codeaurora.org
Cc: kvmarm@lists.cs.columbia.edu
Subject: Re: VCPU hotplug on KVM/ARM
Date: Tue, 27 Feb 2018 11:47:08 +0100	[thread overview]
Message-ID: <20180227104708.GA11391@cbox> (raw)
In-Reply-To: <000e01d3afad$b9a13830$2ce3a890$@codeaurora.org>

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

  reply	other threads:[~2018-02-27 10:40 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-27  9:31 VCPU hotplug on KVM/ARM bthakur
2018-02-27 10:47 ` Christoffer Dall [this message]
2018-02-27 12:04   ` bthakur
2018-02-27 12:46     ` Christoffer Dall
2018-02-27 13:21       ` [Qemu-devel] " Andrew Jones
2018-02-27 13:21         ` Andrew Jones
2018-03-01  9:50         ` [Qemu-devel] " Igor Mammedov
2018-03-01  9:50           ` Igor Mammedov
2018-03-01 10:05           ` [Qemu-devel] [Qemu-arm] " Peter Maydell
2018-03-01 10:05             ` [Qemu-arm] [Qemu-devel] " Peter Maydell
2018-03-01 13:32             ` [Qemu-devel] [Qemu-arm] " David Hildenbrand
2018-03-01 13:32               ` David Hildenbrand
2018-03-07 12:47               ` Marc Zyngier
2018-03-07 12:47                 ` Marc Zyngier
2018-07-24 18:35         ` [Qemu-devel] " Maran Wilson
2018-07-24 18:35           ` Maran Wilson
2018-07-25  6:45           ` [Qemu-devel] " Igor Mammedov
2018-07-25  6:45             ` Igor Mammedov
2018-07-25 10:40           ` Marc Zyngier
2018-07-25 10:40             ` Marc Zyngier
2018-07-25 12:28             ` [Qemu-devel] " Andrew Jones
2018-07-25 12:28               ` Andrew Jones
2018-07-25 13:07               ` Marc Zyngier
2018-07-25 13:07                 ` Marc Zyngier
2018-07-25 17:26                 ` Maran Wilson
2018-07-25 17:26                   ` Maran Wilson
2018-07-31 10:27                 ` Igor Mammedov
2018-07-31 10:27                   ` Igor Mammedov
2018-07-31 10:57                   ` David Hildenbrand
2018-07-31 10:57                     ` David Hildenbrand
2018-08-01  8:09                   ` Bharata B Rao
2018-08-01  8:09                     ` Bharata B Rao

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180227104708.GA11391@cbox \
    --to=cdall@cs.columbia.edu \
    --cc=bthakur@codeaurora.org \
    --cc=kvmarm@lists.cs.columbia.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.