From: Ravi Bangoria <ravi.bangoria@linux.ibm.com>
To: paulus@samba.org, david@gibson.dropbear.id.au
Cc: ravi.bangoria@linux.ibm.com, mpe@ellerman.id.au,
mikey@neuling.org, pbonzini@redhat.com, mst@redhat.com,
clg@kaod.org, qemu-ppc@nongnu.org, qemu-devel@nongnu.org,
kvm@vger.kernel.org, cohuck@redhat.com
Subject: [PATCH v2 0/3] ppc: Enable 2nd DAWR support on Power10
Date: Mon, 29 Mar 2021 09:49:03 +0530 [thread overview]
Message-ID: <20210329041906.213991-1-ravi.bangoria@linux.ibm.com> (raw)
This series enables 2nd DAWR support on p10 qemu guest. 2nd
DAWR is new watchpoint added in Power10 processor. Kernel/kvm
patches are already in[1].
Patches apply fine on qemu/master branch (9e2e9fe3df9f).
v1: https://lore.kernel.org/r/20200723104220.314671-1-ravi.bangoria@linux.ibm.com
[Apologies for long gap]
v1->v2:
- Introduce machine capability cap-dawr1 to enable/disable
the feature. By default, 2nd DAWR is OFF for guests even
when host kvm supports it. User has to manually enable it
with -machine cap-dawr1=on if he wishes to use it.
- Split the header file changes into separate patch. (Sync
headers from v5.12-rc3)
[1] https://git.kernel.org/torvalds/c/bd1de1a0e6eff
Ravi Bangoria (3):
Linux headers: update from 5.12-rc3
ppc: Rename current DAWR macros and variables
ppc: Enable 2nd DAWR support on p10
hw/ppc/spapr.c | 34 ++++++++++
hw/ppc/spapr_caps.c | 32 +++++++++
include/hw/ppc/spapr.h | 8 ++-
include/standard-headers/drm/drm_fourcc.h | 23 ++++++-
include/standard-headers/linux/input.h | 2 +-
include/standard-headers/rdma/vmw_pvrdma-abi.h | 7 ++
linux-headers/asm-generic/unistd.h | 4 +-
linux-headers/asm-mips/unistd_n32.h | 1 +
linux-headers/asm-mips/unistd_n64.h | 1 +
linux-headers/asm-mips/unistd_o32.h | 1 +
linux-headers/asm-powerpc/kvm.h | 2 +
linux-headers/asm-powerpc/unistd_32.h | 1 +
linux-headers/asm-powerpc/unistd_64.h | 1 +
linux-headers/asm-s390/unistd_32.h | 1 +
linux-headers/asm-s390/unistd_64.h | 1 +
linux-headers/asm-x86/kvm.h | 1 +
linux-headers/asm-x86/unistd_32.h | 1 +
linux-headers/asm-x86/unistd_64.h | 1 +
linux-headers/asm-x86/unistd_x32.h | 1 +
linux-headers/linux/kvm.h | 89 ++++++++++++++++++++++++++
linux-headers/linux/vfio.h | 27 ++++++++
target/ppc/cpu.h | 6 +-
target/ppc/kvm.c | 12 ++++
target/ppc/kvm_ppc.h | 7 ++
target/ppc/translate_init.c.inc | 21 +++++-
25 files changed, 274 insertions(+), 11 deletions(-)
--
2.7.4
next reply other threads:[~2021-03-29 4:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-29 4:19 Ravi Bangoria [this message]
2021-03-29 4:19 ` [PATCH v2 1/3] Linux headers: update from 5.12-rc3 Ravi Bangoria
2021-03-29 4:19 ` [PATCH v2 2/3] ppc: Rename current DAWR macros and variables Ravi Bangoria
2021-03-29 4:19 ` [PATCH v2 3/3] ppc: Enable 2nd DAWR support on p10 Ravi Bangoria
2021-03-29 5:04 ` David Gibson
2021-03-29 13:34 ` Ravi Bangoria
2021-03-30 23:49 ` 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=20210329041906.213991-1-ravi.bangoria@linux.ibm.com \
--to=ravi.bangoria@linux.ibm.com \
--cc=clg@kaod.org \
--cc=cohuck@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=kvm@vger.kernel.org \
--cc=mikey@neuling.org \
--cc=mpe@ellerman.id.au \
--cc=mst@redhat.com \
--cc=paulus@samba.org \
--cc=pbonzini@redhat.com \
--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).