From: Fabiano Rosas <farosas@linux.ibm.com>
To: kvm-ppc@vger.kernel.org
Cc: linuxppc-dev@lists.ozlabs.org, christophe.leroy@c-s.fr,
npiggin@gmail.com
Subject: [PATCH v2 0/3] KVM: PPC: Book3S HV: kvmhv_copy_tofrom_guest_radix changes
Date: Thu, 5 Aug 2021 18:26:13 -0300 [thread overview]
Message-ID: <20210805212616.2641017-1-farosas@linux.ibm.com> (raw)
This series contains the fix for __kvmhv_copy_tofrom_guest_radix plus
a couple of changes.
- Patch 1: The fix itself. I thought a smaller fix upfront would be
better to facilitate any backports.
- Patch 2: Adds a sanity check to the low level function. Since the
hcall API already enforces that the effective address must
be on quadrant 0, moving the checks from the high level
function would only add overhead to the hcall path, so I
opted for a lightweight check at the low level.
- Patch 3: Cleans up the EXPORT_SYMBOL_GPL tags. I don't see how they
would be needed since the functions are contained within
kvm-hv.ko.
v1:
https://lkml.kernel.org/r/20210802234941.2568493-1-farosas@linux.ibm.com
Fabiano Rosas (3):
KVM: PPC: Book3S HV: Fix copy_tofrom_guest routines
KVM: PPC: Book3S HV: Add sanity check to copy_tofrom_guest
KVM: PPC: Book3S HV: Stop exporting symbols from book3s_64_mmu_radix
arch/powerpc/kvm/book3s_64_mmu_radix.c | 12 +++++++-----
1 file changed, 7 insertions(+), 5 deletions(-)
--
2.29.2
next reply other threads:[~2021-08-05 21:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-05 21:26 Fabiano Rosas [this message]
2021-08-05 21:26 ` [PATCH v2 1/3] KVM: PPC: Book3S HV: Fix copy_tofrom_guest routines Fabiano Rosas
2021-08-06 10:09 ` Nicholas Piggin
2021-08-05 21:26 ` [PATCH v2 2/3] KVM: PPC: Book3S HV: Add sanity check to copy_tofrom_guest Fabiano Rosas
2021-08-06 10:10 ` Nicholas Piggin
2021-08-05 21:26 ` [PATCH v2 3/3] KVM: PPC: Book3S HV: Stop exporting symbols from book3s_64_mmu_radix Fabiano Rosas
2021-08-27 13:15 ` [PATCH v2 0/3] KVM: PPC: Book3S HV: kvmhv_copy_tofrom_guest_radix changes 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=20210805212616.2641017-1-farosas@linux.ibm.com \
--to=farosas@linux.ibm.com \
--cc=christophe.leroy@c-s.fr \
--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).