qemu-arm.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>,
	Igor Mammedov <imammedo@redhat.com>
Cc: Christoffer Dall <cdall@cs.columbia.edu>,
	QEMU Developers <qemu-devel@nongnu.org>,
	Christoffer Dall <christofferdall@christofferdall.dk>,
	qemu-arm <qemu-arm@nongnu.org>,
	kvmarm@lists.cs.columbia.edu
Subject: Re: [Qemu-devel] [Qemu-arm] VCPU hotplug on KVM/ARM
Date: Thu, 1 Mar 2018 14:32:39 +0100	[thread overview]
Message-ID: <b049a501-cd5e-8c22-9c62-88c950e01b1b@redhat.com> (raw)
In-Reply-To: <CAFEAcA9yaU745Asy--jM0nu8FDJ62CEXSH_TKa-ZZfC16qye6w@mail.gmail.com>

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
_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm

  reply	other threads:[~2018-03-01 13:33 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <000e01d3afad$b9a13830$2ce3a890$@codeaurora.org>
     [not found] ` <20180227104708.GA11391@cbox>
     [not found]   ` <ac329e1b1f5265a805916ab4f8708f9d@codeaurora.org>
     [not found]     ` <20180227124604.GA2373@cbox>
2018-02-27 13:21       ` [Qemu-arm] VCPU hotplug on KVM/ARM Andrew Jones
2018-03-01  9:50         ` [Qemu-arm] [Qemu-devel] " Igor Mammedov
2018-03-01 10:05           ` Peter Maydell
2018-03-01 13:32             ` David Hildenbrand [this message]
2018-03-07 12:47               ` Marc Zyngier
2018-07-24 18:35         ` Maran Wilson
2018-07-25  6:45           ` [Qemu-devel] " Igor Mammedov
2018-07-25 10:40           ` Marc Zyngier
2018-07-25 12:28             ` [Qemu-devel] " Andrew Jones
2018-07-25 13:07               ` Marc Zyngier
2018-07-25 17:26                 ` Maran Wilson
2018-07-31 10:27                 ` Igor Mammedov
2018-07-31 10:57                   ` David Hildenbrand
2018-08-01  8:09                   ` [Qemu-arm] " 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=b049a501-cd5e-8c22-9c62-88c950e01b1b@redhat.com \
    --to=david@redhat.com \
    --cc=cdall@cs.columbia.edu \
    --cc=christofferdall@christofferdall.dk \
    --cc=imammedo@redhat.com \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).