From: Thomas Huth <thuth@redhat.com>
To: Janis Schoetterl-Glausch <scgl@linux.ibm.com>,
qemu-s390x@nongnu.org,
Richard Henderson <richard.henderson@linaro.org>,
David Hildenbrand <david@redhat.com>
Cc: Cornelia Huck <cohuck@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [PATCH v2] target/s390x/tcg: SPX: check validity of new prefix
Date: Wed, 6 Jul 2022 12:17:05 +0200 [thread overview]
Message-ID: <09c2108b-87bb-06a7-3877-7ad15106b32e@redhat.com> (raw)
In-Reply-To: <20220630094340.3646279-1-scgl@linux.ibm.com>
On 30/06/2022 11.43, Janis Schoetterl-Glausch wrote:
> According to the architecture, SET PREFIX must try to access the new
> prefix area and recognize an addressing exception if the area is not
> accessible.
> For qemu this check prevents a crash in cpu_map_lowcore after an
> inaccessible prefix area has been set.
>
> Signed-off-by: Janis Schoetterl-Glausch <scgl@linux.ibm.com>
> Reviewed-by: David Hildenbrand <david@redhat.com>
> ---
> target/s390x/tcg/misc_helper.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/target/s390x/tcg/misc_helper.c b/target/s390x/tcg/misc_helper.c
> index aab9c47747..10dadb002a 100644
> --- a/target/s390x/tcg/misc_helper.c
> +++ b/target/s390x/tcg/misc_helper.c
> @@ -158,6 +158,13 @@ void HELPER(spx)(CPUS390XState *env, uint64_t a1)
> if (prefix == old_prefix) {
> return;
> }
> + /*
> + * Since prefix got aligned to 8k and memory increments are a multiple of
> + * 8k checking the first page is sufficient
> + */
> + if (!mmu_absolute_addr_valid(prefix, true)) {
> + tcg_s390_program_interrupt(env, PGM_ADDRESSING, GETPC());
> + }
>
> env->psa = prefix;
> HELPER_LOG("prefix: %#x\n", prefix);
Thanks, queued to my s390x-next branch now:
https://gitlab.com/thuth/qemu/-/commits/s390x-next
Thomas
prev parent reply other threads:[~2022-07-06 10:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 9:43 [PATCH v2] target/s390x/tcg: SPX: check validity of new prefix Janis Schoetterl-Glausch
2022-07-06 10:17 ` Thomas Huth [this message]
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=09c2108b-87bb-06a7-3877-7ad15106b32e@redhat.com \
--to=thuth@redhat.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=scgl@linux.ibm.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).