From: Pavel Fedin <p.fedin@samsung.com>
To: 'Peter Crosthwaite' <crosthwaitepeter@gmail.com>,
'Peter Maydell' <peter.maydell@linaro.org>
Cc: 'Andrew Jones' <drjones@redhat.com>,
'QEMU Developers' <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] Add mp-affinity property for ARM CPU class
Date: Wed, 14 Oct 2015 09:48:13 +0300 [thread overview]
Message-ID: <00ba01d1064c$4c834ed0$e589ec70$@samsung.com> (raw)
In-Reply-To: <CAPokK=oKKm8RGUoX1dX=-WhSkYX-uTeRf21gCHtsNZWqpVX_jw@mail.gmail.com>
Hello!
> Can we have separate props for each affinity level?
Yes, we can, but i don't see any use for them in this form. Except merging back into full MPIDR value. :)
> Are you assuming MPIDR format for this?
Yes. This is convenient because everything else (KVM, GICv3, etc) also uses MPIDR format. Check out GICv3 live migration RFC v2 for one possible use case.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
next prev parent reply other threads:[~2015-10-14 6:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-09 9:52 [Qemu-devel] [PATCH] Add mp-affinity property for ARM CPU class Pavel Fedin
2015-10-13 17:54 ` Peter Maydell
2015-10-13 20:01 ` Peter Crosthwaite
2015-10-14 6:48 ` Pavel Fedin [this message]
2015-10-14 6:52 ` Pavel Fedin
2015-10-14 19:31 ` 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='00ba01d1064c$4c834ed0$e589ec70$@samsung.com' \
--to=p.fedin@samsung.com \
--cc=crosthwaitepeter@gmail.com \
--cc=drjones@redhat.com \
--cc=peter.maydell@linaro.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).