From: David Hildenbrand <david@redhat.com>
To: qemu-devel@nongnu.org
Cc: rth@twiddle.net, agraf@suse.de,
Aurelien Jarno <aurelien@aurel32.net>,
thuth@redhat.com, david@redhat.com
Subject: [Qemu-devel] [PATCH v1 0/2] PGM injection fix/rework
Date: Fri, 9 Jun 2017 16:21:54 +0200 [thread overview]
Message-ID: <20170609142156.18767-1-david@redhat.com> (raw)
We have various places where we inject suppressing PGM exceptions,
but don't forward the PSW. Let's fix that by detecting whether to
forward the PSW using the interception code.
We can now get rid of ILEN_LATER/ILEN_LATER_INC and replace it by
ILEN_AUTO, to automatically detect the instruction length using the
current PSW.
ILEN_AUTO is also used with program_interrupt(), so let's add it at the
right place.
To correctly identify nullifying PER events (and also that the guest can
identify them), we have to set the PER flag PER_CODE_EVENT_NULLIFICATION
accordingly.
This e.g. fixes TB (TEST BLOCK) program interrupts in Thomas' interception
handler kvm-unit-test.
David Hildenbrand (2):
target/s390x: correctly indicate PER nullification
target/s390x: rework PGM interrupt psw.addr handling
target/s390x/cpu.h | 7 ++-----
target/s390x/helper.c | 46 +++++++++++++++++++++++++++++++++++-----------
target/s390x/misc_helper.c | 22 +++++++++-------------
target/s390x/mmu_helper.c | 6 +++---
target/s390x/translate.c | 3 +--
5 files changed, 50 insertions(+), 34 deletions(-)
--
2.9.3
next reply other threads:[~2017-06-09 14:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-09 14:21 David Hildenbrand [this message]
2017-06-09 14:21 ` [Qemu-devel] [PATCH v1 1/2] target/s390x: correctly indicate PER nullification David Hildenbrand
2017-06-09 14:21 ` [Qemu-devel] [PATCH v1 2/2] target/s390x: rework PGM interrupt psw.addr handling David Hildenbrand
2017-06-09 20:39 ` [Qemu-devel] [PATCH v1 0/2] PGM injection fix/rework Richard Henderson
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=20170609142156.18767-1-david@redhat.com \
--to=david@redhat.com \
--cc=agraf@suse.de \
--cc=aurelien@aurel32.net \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=thuth@redhat.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).