From: Ilya Leoshkevich <iii@linux.ibm.com>
To: Christian Borntraeger <borntraeger@linux.ibm.com>,
Janosch Frank <frankja@linux.ibm.com>,
Claudio Imbrenda <imbrenda@linux.ibm.com>,
Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>
Cc: David Hildenbrand <david@redhat.com>,
Sven Schnelle <svens@linux.ibm.com>,
kvm@vger.kernel.org, linux-s390@vger.kernel.org,
linux-kernel@vger.kernel.org,
Jens Freimann <jfreimann@redhat.com>,
Ilya Leoshkevich <iii@linux.ibm.com>
Subject: [PATCH 0/2] KVM: s390: interrupt: Fix stepping into interrupt handlers
Date: Thu, 29 Jun 2023 10:32:03 +0200 [thread overview]
Message-ID: <20230629083452.183274-1-iii@linux.ibm.com> (raw)
Hi,
I tried to compare the behavior of KVM and TCG by diffing instruction
traces, and found two issues in KVM related to stepping into interrupt
handlers.
I'm not very familiar with the KVM code base, so please let me know if
the fixes can be improved or if these problems need to be handled
completely differently.
Best regards,
Ilya
Ilya Leoshkevich (2):
KVM: s390: interrupt: Fix stepping into interrupt handlers
KVM: s390: interrupt: Fix stepping into program interrupt handlers
arch/s390/kvm/intercept.c | 19 +++++++++++++++++--
arch/s390/kvm/interrupt.c | 10 ++++++++++
arch/s390/kvm/kvm-s390.c | 4 ++--
3 files changed, 29 insertions(+), 4 deletions(-)
--
2.41.0
next reply other threads:[~2023-06-29 8:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-29 8:32 Ilya Leoshkevich [this message]
2023-06-29 8:32 ` [PATCH 1/2] KVM: s390: interrupt: Fix stepping into interrupt handlers Ilya Leoshkevich
2023-06-29 8:32 ` [PATCH 2/2] KVM: s390: interrupt: Fix stepping into program " Ilya Leoshkevich
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=20230629083452.183274-1-iii@linux.ibm.com \
--to=iii@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=jfreimann@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=svens@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).