From: Peter Maydell <peter.maydell@linaro.org>
To: Igor Mammedov <imammedo@redhat.com>
Cc: Andrew Jones <drjones@redhat.com>,
bthakur@codeaurora.org, Christoffer Dall <cdall@cs.columbia.edu>,
Christoffer Dall <cdall@kernel.org>,
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 10:05:09 +0000 [thread overview]
Message-ID: <CAFEAcA9yaU745Asy--jM0nu8FDJ62CEXSH_TKa-ZZfC16qye6w@mail.gmail.com> (raw)
In-Reply-To: <20180301105030.2b716e68@redhat.com>
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
WARNING: multiple messages have this Message-ID (diff)
From: Peter Maydell <peter.maydell@linaro.org>
To: 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-arm] [Qemu-devel] VCPU hotplug on KVM/ARM
Date: Thu, 1 Mar 2018 10:05:09 +0000 [thread overview]
Message-ID: <CAFEAcA9yaU745Asy--jM0nu8FDJ62CEXSH_TKa-ZZfC16qye6w@mail.gmail.com> (raw)
In-Reply-To: <20180301105030.2b716e68@redhat.com>
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
next prev parent reply other threads:[~2018-03-01 10:05 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
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 ` Peter Maydell [this message]
2018-03-01 10:05 ` [Qemu-arm] " 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=CAFEAcA9yaU745Asy--jM0nu8FDJ62CEXSH_TKa-ZZfC16qye6w@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=bthakur@codeaurora.org \
--cc=cdall@cs.columbia.edu \
--cc=cdall@kernel.org \
--cc=christofferdall@christofferdall.dk \
--cc=drjones@redhat.com \
--cc=imammedo@redhat.com \
--cc=kvmarm@lists.cs.columbia.edu \
--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 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.