From: Michael Bringmann <mwb@linux.vnet.ibm.com>
To: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org
Cc: Rob Herring <robh@kernel.org>,
Mike Rapoport <rppt@linux.vnet.ibm.com>,
tlfalcon@linux.vnet.ibm.com,
Srikar Dronamraju <srikar@linux.vnet.ibm.com>,
Nicholas Piggin <npiggin@gmail.com>,
Vaidyanathan Srinivasan <svaidyan@in.ibm.com>,
mwb@linux.vnet.ibm.com, minkim@us.ibm.com,
Paul Mackerras <paulus@samba.org>,
tyreld@linux.vnet.ibm.com,
Andrew Morton <akpm@linux-foundation.org>,
Guenter Roeck <linux@roeck-us.net>
Subject: [RFC 0/3] powerpc/pseries: Remap hw to kernel cpu indexes
Date: Tue, 11 Dec 2018 16:03:31 -0600 [thread overview]
Message-ID: <20181211220321.87502.72082.stgit@powerkvm6.aus.stglabs.ibm.com> (raw)
Define and apply new interface to map hardware-specific powerpc cpu
ids to a kernel specific range of cpu values. Mapping is intended
to prevent confusion within the kernel about the cpu+node mapping,
and the changes in configuration that may happen due to powerpc LPAR
migration or other associativity changes during the lifetime of a
system. These interfaces exchange the thread_index provided by the
'ibm,ppc-interrupt-server#s' properties, for an internal index to
be used by kernel scheduling interfaces.
Signed-off-by: Michael Bringmann <mwb@linux.vnet.ibm.com>
Michael Bringmann (3):
powerpc/numa: Conditionally online new nodes
powerpc/numa: Define mapping between HW and kernel cpus
powerpc/numa: Apply mapping between HW and kernel cpu
next reply other threads:[~2018-12-11 22:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-11 22:03 Michael Bringmann [this message]
2018-12-11 22:03 ` [RFC 1/3] powerpc/numa: Conditionally online new nodes Michael Bringmann
2018-12-11 22:03 ` [RFC 2/3] powerpc/numa: Define mapping between HW and kernel cpus Michael Bringmann
2018-12-11 22:04 ` [RFC 3/3] powerpc/numa: Apply " Michael Bringmann
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=20181211220321.87502.72082.stgit@powerkvm6.aus.stglabs.ibm.com \
--to=mwb@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=minkim@us.ibm.com \
--cc=npiggin@gmail.com \
--cc=paulus@samba.org \
--cc=robh@kernel.org \
--cc=rppt@linux.vnet.ibm.com \
--cc=srikar@linux.vnet.ibm.com \
--cc=svaidyan@in.ibm.com \
--cc=tlfalcon@linux.vnet.ibm.com \
--cc=tyreld@linux.vnet.ibm.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).