linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: marc.zyngier@arm.com (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH] arm64: KVM: Allow userspace to configure guest MPIDR_EL1
Date: Wed, 20 Apr 2016 18:33:54 +0100	[thread overview]
Message-ID: <20160420183354.31f1bfbd@arm.com> (raw)
In-Reply-To: <1461161319-38835-1-git-send-email-ashoks@broadcom.com>

On Wed, 20 Apr 2016 07:08:39 -0700
Ashok Kumar <ashoks@broadcom.com> wrote:

> For guests with NUMA configuration, Node ID needs to
> be recorded in the respective affinity byte of MPIDR_EL1.

As others have said before, the mapping between the NUMA hierarchy and
MPIDR_EL1 are completely arbitrary, and only the firmware description
can help the kernel in interpreting the affinity levels.

If you want any patch like this one to be considered, I'd like to see
the corresponding userspace that:

- programs the affinity into the vcpus,
- pins the vcpus to specific physical CPUs,
- exposes the corresponding firmware description (either DT or ACPI) to
  the kernel.

Short of having all these elements together, there is little point in
letting userspace messing with the guest's affinity registers.

Thanks,

	M.
-- 
Jazz is not dead. It just smells funny.

  parent reply	other threads:[~2016-04-20 17:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-20 14:08 [RFC PATCH] arm64: KVM: Allow userspace to configure guest MPIDR_EL1 Ashok Kumar
2016-04-20 14:38 ` Mark Rutland
2016-04-20 14:39 ` Andrew Jones
2016-04-20 17:33 ` Marc Zyngier [this message]
2016-04-21  7:04   ` Andrew Jones
2016-04-21  9:25     ` Marc Zyngier
2016-04-21  9:56       ` Andrew Jones
2016-04-21 11:46         ` Ashok Kumar

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=20160420183354.31f1bfbd@arm.com \
    --to=marc.zyngier@arm.com \
    --cc=linux-arm-kernel@lists.infradead.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).