From: Fabiano Rosas <farosas@linux.ibm.com>
To: kvm-ppc@vger.kernel.org
Cc: linuxppc-dev@lists.ozlabs.org, npiggin@gmail.com, aik@ozlabs.ru
Subject: [PATCH v4 0/5] KVM: PPC: MMIO fixes
Date: Fri, 21 Jan 2022 19:26:21 -0300 [thread overview]
Message-ID: <20220121222626.972495-1-farosas@linux.ibm.com> (raw)
Changes from v3:
Removed all of the low level messages and altered the pr_emerg in the
emulate_mmio to a more descriptive message.
Changed the Program interrupt to a Data Storage. There's an ifdef
needed because this code is shared by HV, PR and booke.
v3:
https://lore.kernel.org/r/20220107210012.4091153-1-farosas@linux.ibm.com
v2:
https://lore.kernel.org/r/20220106200304.4070825-1-farosas@linux.ibm.com
v1:
https://lore.kernel.org/r/20211223211528.3560711-1-farosas@linux.ibm.com
Fabiano Rosas (5):
KVM: PPC: Book3S HV: Stop returning internal values to userspace
KVM: PPC: Fix vmx/vsx mixup in mmio emulation
KVM: PPC: mmio: Reject instructions that access more than mmio.data
size
KVM: PPC: mmio: Return to guest after emulation failure
KVM: PPC: mmio: Deliver DSI after emulation failure
arch/powerpc/kvm/emulate_loadstore.c | 10 ++----
arch/powerpc/kvm/powerpc.c | 46 ++++++++++++++++++----------
2 files changed, 33 insertions(+), 23 deletions(-)
--
2.34.1
next reply other threads:[~2022-01-21 22:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-21 22:26 Fabiano Rosas [this message]
2022-01-21 22:26 ` [PATCH v4 1/5] KVM: PPC: Book3S HV: Stop returning internal values to userspace Fabiano Rosas
2022-01-21 22:26 ` [PATCH v4 2/5] KVM: PPC: Fix vmx/vsx mixup in mmio emulation Fabiano Rosas
2022-01-21 22:26 ` [PATCH v4 3/5] KVM: PPC: mmio: Reject instructions that access more than mmio.data size Fabiano Rosas
2022-01-25 3:06 ` Nicholas Piggin
2022-01-21 22:26 ` [PATCH v4 4/5] KVM: PPC: mmio: Return to guest after emulation failure Fabiano Rosas
2022-01-25 3:26 ` Nicholas Piggin
2022-01-21 22:26 ` [PATCH v4 5/5] KVM: PPC: mmio: Deliver DSI " Fabiano Rosas
2022-01-25 3:39 ` Nicholas Piggin
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=20220121222626.972495-1-farosas@linux.ibm.com \
--to=farosas@linux.ibm.com \
--cc=aik@ozlabs.ru \
--cc=kvm-ppc@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=npiggin@gmail.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).