From: Pavel Fedin <p.fedin@samsung.com>
To: 'Igor Mammedov' <imammedo@redhat.com>
Cc: peter.maydell@linaro.org, qemu-devel@nongnu.org,
'Ashok Kumar' <ashoks@broadcom.com>,
'Shlomo Pongratz' <shlomo.pongratz@huawei.com>
Subject: Re: [Qemu-devel] [PATCH] Use Aff1 with mpidr
Date: Fri, 29 May 2015 15:26:57 +0300 [thread overview]
Message-ID: <01ab01d09a0a$c1bdb450$45391cf0$@samsung.com> (raw)
In-Reply-To: <20150529111858.4b7b0db9@nial.brq.redhat.com>
Hello!
> That's what I see as correct way to go
> and along the way teach KVM to not derive mpidr encoding from vcpuid
> and use QEMU provided mpidr value, that way mpidr would be consistent.
Yes, and this would make modelling of real hardware working much better. However,
unfortunately, i have just tested it, and it does not work. MPIDR can be set for the vCPU,
and i believe it will even give back the value when read. But PSCI completely ignores this
setting.
> As it currently stands QEMU notion of mpidr and KVM's will diverge
> onece CPU count goes above 16 CPUs.
Yes, but fortunately the code which cares about it (PSCI and Shlomo's GICv3 software
emulation) is not used with KVM. So i think we have no other choice if we want to be
compatible with current KVM APIs.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
next prev parent reply other threads:[~2015-05-29 12:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-22 10:32 [Qemu-devel] [PATCH] Use Aff1 with mpidr Pavel Fedin
2015-05-28 14:57 ` Shlomo Pongratz
2015-05-29 6:45 ` Pavel Fedin
2015-05-31 11:03 ` Shlomo Pongratz
2015-06-01 6:34 ` Pavel Fedin
2015-06-01 9:03 ` Pavel Fedin
2015-06-01 14:26 ` Shlomo Pongratz
2015-06-02 6:29 ` Pavel Fedin
2015-06-02 15:37 ` Igor Mammedov
2015-05-29 8:36 ` Igor Mammedov
2015-05-29 8:53 ` Pavel Fedin
2015-05-29 9:18 ` Igor Mammedov
2015-05-29 12:26 ` Pavel Fedin [this message]
2015-05-29 13:03 ` Igor Mammedov
2015-05-29 13:41 ` Pavel Fedin
2015-06-02 15:32 ` Igor Mammedov
2015-06-02 15:42 ` Peter Maydell
2015-06-02 15:54 ` Igor Mammedov
2015-05-29 17:37 ` Pavel Fedin
2015-05-30 2:30 ` Shannon Zhao
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='01ab01d09a0a$c1bdb450$45391cf0$@samsung.com' \
--to=p.fedin@samsung.com \
--cc=ashoks@broadcom.com \
--cc=imammedo@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=shlomo.pongratz@huawei.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).