From: Nicholas Piggin <npiggin@gmail.com>
To: linuxppc-dev@ozlabs.org
Cc: Michael Neuling <mikey@neuling.org>,
kvm@vger.kernel.org, Nicholas Piggin <npiggin@gmail.com>
Subject: [PATCH v2 0/2] KVM: PPC: Book3S HV: Injected interrupt SRR1
Date: Thu, 30 Mar 2023 20:32:22 +1000 [thread overview]
Message-ID: <20230330103224.3589928-1-npiggin@gmail.com> (raw)
I missed this in my earlier review and testing, but I think we need
these in the prefix instruction enablement series before the final patch
that enables HFSCR[PREFIX] for guests.
Thanks,
Nick
Nicholas Piggin (2):
KVM: PPC: Permit SRR1 flags in more injected interrupt types
KVM: PPC: Book3S HV: Set SRR1[PREFIX] bit on injected interrupts
arch/powerpc/include/asm/kvm_ppc.h | 27 ++++++++++++++--------
arch/powerpc/kvm/book3s.c | 32 +++++++++++++-------------
arch/powerpc/kvm/book3s_64_mmu_radix.c | 13 +++++++----
arch/powerpc/kvm/book3s_hv.c | 23 ++++++++++++------
arch/powerpc/kvm/book3s_hv_nested.c | 9 +++++---
arch/powerpc/kvm/book3s_pr.c | 4 ++--
arch/powerpc/kvm/booke.c | 13 +++++++----
arch/powerpc/kvm/emulate_loadstore.c | 6 ++---
arch/powerpc/kvm/powerpc.c | 4 +++-
9 files changed, 81 insertions(+), 50 deletions(-)
--
2.37.2
next reply other threads:[~2023-03-30 10:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 10:32 Nicholas Piggin [this message]
2023-03-30 10:32 ` [PATCH v2 1/2] KVM: PPC: Permit SRR1 flags in more injected interrupt types Nicholas Piggin
2023-04-02 0:27 ` kernel test robot
2023-03-30 10:32 ` [PATCH v2 2/2] KVM: PPC: Book3S HV: Set SRR1[PREFIX] bit on injected interrupts Nicholas Piggin
2023-04-06 0:34 ` [PATCH v2 0/2] KVM: PPC: Book3S HV: Injected interrupt SRR1 Michael Ellerman
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=20230330103224.3589928-1-npiggin@gmail.com \
--to=npiggin@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mikey@neuling.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).