From: Marc Zyngier <marc.zyngier@arm.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Shlomo Pongratz <shlomo.pongratz@huawei.com>,
Shlomo Pongratz <shlomopongratz@gmail.com>,
Pavel Fedin <p.fedin@samsung.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Shannon Zhao <shannon.zhao@linaro.org>,
Ashok Kumar <ashoks@broadcom.com>,
Igor Mammedov <imammedo@redhat.com>,
"kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>
Subject: Re: [Qemu-devel] should KVM or userspace be the one which decides what MIPIDR/affinity values to assign to vcpus?
Date: Tue, 09 Jun 2015 15:35:21 +0100 [thread overview]
Message-ID: <5576F9A9.6010501@arm.com> (raw)
In-Reply-To: <CAFEAcA-GAsd7vWsmmZm6ikw+rRK2p7S3uNWBwYzTUGum12pyNA@mail.gmail.com>
On 09/06/15 15:01, Peter Maydell wrote:
> On 9 June 2015 at 15:00, Marc Zyngier <marc.zyngier@arm.com> wrote:
>>
>> Yeah, what I had in mind was something along the lines of:
>> - kernel computes its "default MPDIR"
>> - kernel exposes a new capability "KVM_ARM_ALLOW_MPIDR_OVERRIDE" (or
>> something along those lines)
>> - userspace does the right thing.
>
> You forgot the "???" step :-)
Indeed. I also missed the step that says "kernel is able to convert
arbitrary MPIDR to vcpu_id in an efficient manner...". GICv3 is
definitely going to require this.
N,
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2015-06-09 14:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-08 10:52 [Qemu-devel] should KVM or userspace be the one which decides what MIPIDR/affinity values to assign to vcpus? Peter Maydell
2015-06-09 10:52 ` Marc Zyngier
2015-06-09 11:24 ` Peter Maydell
2015-06-09 11:54 ` Igor Mammedov
2015-06-09 12:27 ` Marc Zyngier
2015-06-09 13:16 ` Peter Maydell
2015-06-09 14:00 ` Marc Zyngier
2015-06-09 14:01 ` Peter Maydell
2015-06-09 14:35 ` Marc Zyngier [this message]
2015-06-10 9:54 ` Igor Mammedov
2015-06-10 10:31 ` Marc Zyngier
2015-06-10 11:22 ` Radim
2015-06-25 8:00 ` Christoffer Dall
2015-06-25 9:06 ` Peter Maydell
2015-06-25 12:41 ` Christoffer Dall
2015-06-25 12:51 ` Peter Maydell
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=5576F9A9.6010501@arm.com \
--to=marc.zyngier@arm.com \
--cc=ashoks@broadcom.com \
--cc=imammedo@redhat.com \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=p.fedin@samsung.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=shannon.zhao@linaro.org \
--cc=shlomo.pongratz@huawei.com \
--cc=shlomopongratz@gmail.com \
/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).