From: Suraj Jitindar Singh <sjitindarsingh@gmail.com>
To: qemu-ppc@nongnu.org
Cc: qemu-devel@nongnu.org, david@gibson.dropbear.id.au,
paulus@ozlabs.org,
Suraj Jitindar Singh <sjitindarsingh@gmail.com>
Subject: [Qemu-devel] [QEMU-PPC] [PATCH V5 0/7] target/ppc: Rework spapr_caps
Date: Fri, 19 Jan 2018 15:59:58 +1100 [thread overview]
Message-ID: <20180119050005.29392-1-sjitindarsingh@gmail.com> (raw)
The following patch series adds 3 new tristate capabilities and their
associated handling.
A new H-Call is implemented which a guest will use to query the
requirement for and availability of workarounds for certain cpu
behaviours.
Applies on top of David's tree: ppc-for-2.12
The main changes to V5 are:
- Add patch 2/7 to series to introduce macros to generate migration fields
- Fix bisect breakage in 3/7 due to unused function
- Use assert in 7/7 for invalid cap values
Suraj Jitindar Singh (7):
target/ppc/kvm: Add cap_ppc_safe_[cache/bounds_check/indirect_branch]
target/ppc/spapr_caps: Add macro to generate spapr_caps migration
vmstate
target/ppc/spapr_caps: Add support for tristate spapr_capabilities
target/ppc/spapr_caps: Add new tristate cap safe_cache
target/ppc/spapr_caps: Add new tristate cap safe_bounds_check
target/ppc/spapr_caps: Add new tristate cap safe_indirect_branch
target/ppc/spapr: Add H-Call H_GET_CPU_CHARACTERISTICS
hw/ppc/spapr.c | 6 ++
hw/ppc/spapr_caps.c | 202 +++++++++++++++++++++++++++++-----------
hw/ppc/spapr_hcall.c | 58 ++++++++++++
include/hw/ppc/spapr.h | 28 +++++-
linux-headers/asm-powerpc/kvm.h | 8 ++
linux-headers/linux/kvm.h | 3 +
target/ppc/kvm.c | 58 ++++++++++++
target/ppc/kvm_ppc.h | 18 ++++
8 files changed, 326 insertions(+), 55 deletions(-)
--
2.13.6
next reply other threads:[~2018-01-19 5:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-19 4:59 Suraj Jitindar Singh [this message]
2018-01-19 4:59 ` [Qemu-devel] [QEMU-PPC] [PATCH V5 1/7] target/ppc/kvm: Add cap_ppc_safe_[cache/bounds_check/indirect_branch] Suraj Jitindar Singh
2018-01-19 5:00 ` [Qemu-devel] [QEMU-PPC] [PATCH V5 2/7] target/ppc/spapr_caps: Add macro to generate spapr_caps migration vmstate Suraj Jitindar Singh
2018-01-19 5:09 ` David Gibson
2018-01-19 5:18 ` Alexey Kardashevskiy
2018-01-28 23:43 ` Suraj Jitindar Singh
2018-01-29 3:03 ` Alexey Kardashevskiy
2018-01-30 6:19 ` Suraj Jitindar Singh
2018-01-19 5:00 ` [Qemu-devel] [QEMU-PPC] [PATCH V5 3/7] target/ppc/spapr_caps: Add support for tristate spapr_capabilities Suraj Jitindar Singh
2018-01-19 5:00 ` [Qemu-devel] [QEMU-PPC] [PATCH V5 4/7] target/ppc/spapr_caps: Add new tristate cap safe_cache Suraj Jitindar Singh
2018-01-19 5:00 ` [Qemu-devel] [QEMU-PPC] [PATCH V5 5/7] target/ppc/spapr_caps: Add new tristate cap safe_bounds_check Suraj Jitindar Singh
2018-01-19 5:00 ` [Qemu-devel] [QEMU-PPC] [PATCH V5 6/7] target/ppc/spapr_caps: Add new tristate cap safe_indirect_branch Suraj Jitindar Singh
2018-01-19 5:00 ` [Qemu-devel] [QEMU-PPC] [PATCH V5 7/7] target/ppc/spapr: Add H-Call H_GET_CPU_CHARACTERISTICS Suraj Jitindar Singh
2018-01-19 5:29 ` [Qemu-devel] [QEMU-PPC] [PATCH V5 0/7] target/ppc: Rework spapr_caps no-reply
2018-01-29 0:36 ` David Gibson
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=20180119050005.29392-1-sjitindarsingh@gmail.com \
--to=sjitindarsingh@gmail.com \
--cc=david@gibson.dropbear.id.au \
--cc=paulus@ozlabs.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).