From: Christoffer Dall <christoffer.dall@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Marc Zyngier <marc.zyngier@arm.com>,
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: Thu, 25 Jun 2015 14:41:13 +0200 [thread overview]
Message-ID: <20150625124113.GF28244@cbox> (raw)
In-Reply-To: <CAFEAcA_cDT7r-LrX+4vYD5DSK6wTYbDTqoDm2B9gaS3ftJTqJg@mail.gmail.com>
On Thu, Jun 25, 2015 at 10:06:20AM +0100, Peter Maydell wrote:
> On 25 June 2015 at 09:00, Christoffer Dall <christoffer.dall@linaro.org> wrote:
> > Of course, KVM can deny an unsupported configuration, but I am wondering
> > if we really think anybody will care about the 'model such specific
> > hardware' aspect with KVM, or if we should only consider the 'I want a
> > VM with x VCPUs' scenario, in which case the second option below seems
> > simpler to me.
>
> I agree it's not very likely anybody cares about the specific cluster
> topology. However if we don't want to support arbitrary topologies
> then QEMU is going to end up in the business of editing the user
> supplied device tree blob to make its cpu definitions match up with
> whatever the kernel provides, which could be pretty tedious.
>
I see, then you can't easily contruct a machine and a DT in one go
before talking to KVM.
Oh well, I don't feel strongly one way or the other.
-Christoffer
next prev parent reply other threads:[~2015-06-25 12:41 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
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 [this message]
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=20150625124113.GF28244@cbox \
--to=christoffer.dall@linaro.org \
--cc=ashoks@broadcom.com \
--cc=imammedo@redhat.com \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=marc.zyngier@arm.com \
--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).