From: Michael Neuling <mikey@neuling.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Alexander Graf <agraf@suse.de>
Cc: linuxppc-dev@lists.ozlabs.org, Paul Mackerras <paulus@samba.org>,
kvm-ppc@vger.kernel.org, kvm@vger.kernel.org
Subject: [PATCH v2 0/6] Implement split core for POWER8
Date: Fri, 23 May 2014 18:15:24 +1000 [thread overview]
Message-ID: <1400832930-17050-1-git-send-email-mikey@neuling.org> (raw)
This patch series implements split core mode on POWER8. This enables up to 4
subcores per core which can each independently run guests (per guest SPRs like
SDR1, LPIDR etc are replicated per subcore). Lots more documentation on this
feature in the code and commit messages.
Most of this code is in the powernv platform but there's a couple of KVM
specific patches too.
Patch series authored by mpe and me with a few bug fixes from others.
v2:
There are some minor updates based on comments and I've added the Acks by
Paulus and Alex for the KVM code.
next reply other threads:[~2014-05-23 8:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-23 8:15 Michael Neuling [this message]
2014-05-23 8:15 ` [PATCH v2 1/6] KVM: PPC: Book3S HV: Rework the secondary inhibit code Michael Neuling
2014-05-23 8:15 ` [PATCH v2 2/6] powerpc/powernv: Make it possible to skip the IRQHAPPENED check in power7_nap() Michael Neuling
2014-05-23 8:15 ` [PATCH v2 3/6] powerpc: Add threads_per_subcore Michael Neuling
2014-05-23 8:15 ` [PATCH v2 4/6] powerpc: Check cpu_thread_in_subcore() in __cpu_up() Michael Neuling
2014-05-23 8:15 ` [PATCH v2 5/6] KVM: PPC: Book3S HV: Use threads_per_subcore in KVM Michael Neuling
2014-05-23 8:15 ` [PATCH v2 6/6] powerpc/powernv: Add support for POWER8 split core on powernv Michael Neuling
2014-05-23 9:53 ` [PATCH v2 0/6] Implement split core for POWER8 Alexander Graf
2014-05-23 10:00 ` Michael Neuling
2014-05-23 10:05 ` Alexander Graf
2014-05-23 10:11 ` Michael Neuling
2014-05-23 10:27 ` Alexander Graf
2014-05-23 10:50 ` Michael Neuling
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=1400832930-17050-1-git-send-email-mikey@neuling.org \
--to=mikey@neuling.org \
--cc=agraf@suse.de \
--cc=benh@kernel.crashing.org \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.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).