From: Nicholas Piggin <npiggin@gmail.com>
To: qemu-ppc@nongnu.org
Cc: qemu-devel@nongnu.org, Nicholas Piggin <npiggin@gmail.com>
Subject: [RFC PATCH 1/3] target/ppc: raise HV interrupts for partition table entry problems
Date: Thu, 10 Feb 2022 16:53:38 +1000 [thread overview]
Message-ID: <20220210065340.1276367-2-npiggin@gmail.com> (raw)
In-Reply-To: <20220210065340.1276367-1-npiggin@gmail.com>
These are an HV exception. Not 100% sure what HDSISR bits to set in case of
an empty table -- not sure what hardware does.
not-yet-Signed-off-by: Nicholas Piggin <npiggin@gmail.com>
---
target/ppc/mmu-radix64.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/target/ppc/mmu-radix64.c b/target/ppc/mmu-radix64.c
index 040c055bff..54fb3ce98d 100644
--- a/target/ppc/mmu-radix64.c
+++ b/target/ppc/mmu-radix64.c
@@ -560,13 +560,13 @@ static bool ppc_radix64_xlate_impl(PowerPCCPU *cpu, vaddr eaddr,
} else {
if (!ppc64_v3_get_pate(cpu, lpid, &pate)) {
if (guest_visible) {
- ppc_radix64_raise_si(cpu, access_type, eaddr, DSISR_NOPTE);
+ ppc_radix64_raise_hsi(cpu, access_type, eaddr, eaddr, DSISR_R_BADCONFIG);
}
return false;
}
if (!validate_pate(cpu, lpid, &pate)) {
if (guest_visible) {
- ppc_radix64_raise_si(cpu, access_type, eaddr, DSISR_R_BADCONFIG);
+ ppc_radix64_raise_hsi(cpu, access_type, eaddr, eaddr, DSISR_R_BADCONFIG);
}
return false;
}
--
2.23.0
next prev parent reply other threads:[~2022-02-10 7:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-10 6:53 [RFC PATCH 0/3] spapr: nested-hv support for TCG Nicholas Piggin
2022-02-10 6:53 ` Nicholas Piggin [this message]
2022-02-10 6:53 ` [RFC PATCH 2/3] spapr: prevent hdec timer being set up under virtual hypervisor Nicholas Piggin
2022-02-10 6:53 ` [RFC PATCH 3/3] spapr: implement nested-hv support for the TCG " Nicholas Piggin
2022-02-14 14:32 ` Fabiano Rosas
2022-02-14 23:24 ` Nicholas Piggin
2022-02-14 18:31 ` Cédric Le Goater
2022-02-14 23:28 ` Nicholas Piggin
2022-02-15 2:57 ` 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=20220210065340.1276367-2-npiggin@gmail.com \
--to=npiggin@gmail.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).