From: Fabiano Rosas <farosas@linux.ibm.com>
To: kvm-ppc@vger.kernel.org
Cc: linuxppc-dev@lists.ozlabs.org, npiggin@gmail.com
Subject: [PATCH v3 0/2] KVM: PPC: Book3S HV: Nested guest HFSCR changes
Date: Thu, 15 Apr 2021 20:09:46 -0300 [thread overview]
Message-ID: <20210415230948.3563415-1-farosas@linux.ibm.com> (raw)
Applied Nick's suggestions and added a new patch for the Cause bits
issue.
I'm thinking maybe the approach of crashing L1 when L2 tries to access
a facility that L0 has denied is too heavy-handed. But on the other
hand, if L1 were to access the facility itself, the same thing would
happen and L2 runs "inside of L1" in a sense.
Currently, both L0 and L1s handle only msgsndp. All other HV Facility
Unavailable causes are already met with a Program interrupt.
Changes since v2:
- removed the sanitise functions
- moved the entry code into a new load_l2_hv_regs and the exit code
into the existing save_hv_return_state
- new patch: removes the cause bits when L0 has disabled the
corresponding facility
v2:
- made the change more generic, not only applies to hfscr anymore;
- sanitisation is now done directly on the vcpu struct, l2_hv is left unchanged;
https://lkml.kernel.org/r/20210406214645.3315819-1-farosas@linux.ibm.com
v1:
https://lkml.kernel.org/r/20210305231055.2913892-1-farosas@linux.ibm.com
Fabiano Rosas (2):
KVM: PPC: Book3S HV: Sanitise vcpu registers in nested path
KVM: PPC: Book3S HV: Stop forwarding all HFSCR cause bits to L1
arch/powerpc/kvm/book3s_hv_nested.c | 72 ++++++++++++++++++++---------
1 file changed, 51 insertions(+), 21 deletions(-)
--
2.29.2
next reply other threads:[~2021-04-15 23:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-15 23:09 Fabiano Rosas [this message]
2021-04-15 23:09 ` [PATCH v3 1/2] KVM: PPC: Book3S HV: Sanitise vcpu registers in nested path Fabiano Rosas
2021-05-01 1:58 ` Nicholas Piggin
2021-05-04 4:28 ` Paul Mackerras
2021-05-04 5:26 ` Nicholas Piggin
2021-05-04 7:36 ` Paul Mackerras
2021-05-04 8:35 ` Nicholas Piggin
2021-05-04 18:37 ` Fabiano Rosas
2021-05-01 4:48 ` Nicholas Piggin
2021-04-15 23:09 ` [PATCH v3 2/2] KVM: PPC: Book3S HV: Stop forwarding all HFSCR cause bits to L1 Fabiano Rosas
2021-05-01 2:04 ` 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=20210415230948.3563415-1-farosas@linux.ibm.com \
--to=farosas@linux.ibm.com \
--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).