From: Janosch Frank <frankja@linux.ibm.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>,
David Hildenbrand <david@redhat.com>
Cc: kvm@vger.kernel.org, linux-s390@vger.kernel.org, thuth@redhat.com
Subject: Re: [kvm-unit-tests PATCH 0/2] s390x: Improve architectural compliance for diag308
Date: Tue, 5 Nov 2019 19:37:33 +0100 [thread overview]
Message-ID: <2cb61837-dc0e-2b9f-cf40-1abb430af404@linux.ibm.com> (raw)
In-Reply-To: <0560e27d-dac8-a569-2e3f-f8188724c822@de.ibm.com>
[-- Attachment #1.1: Type: text/plain, Size: 1477 bytes --]
On 11/5/19 7:23 PM, Christian Borntraeger wrote:
>
>
> On 05.11.19 18:34, David Hildenbrand wrote:
>>
>>
>>> Am 05.11.2019 um 17:29 schrieb Janosch Frank <frankja@linux.ibm.com>:
>>>
>>> When testing diag308 subcodes 0/1 on lpar with virtual mem set up, I
>>> experienced spec PGMs and addressing PGMs due to the tests not setting
>>> short psw bit 12 and leaving the DAT bit on.
>>>
>>> The problem was not found under KVM/QEMU, because Qemu just ignores
>>> all cpu mask bits... I'm working on a fix for that too.
>>>
>>
>> I don‘t have access to documentation. Is what LPAR does documented behavior or is this completely undocumented and therefore undefined behavior? Then we should remove these test cases completely instead.
>
> Yes. It was just that KVM/QEMU never looked at the mask and just used a default
> one. The short PSW on address 0 clearly contains a mask and we should better set
> it.
Yeah, we're currently reviewing the QEMU patch to fix this, I'll send it
out tomorrow.
>>
>>> Janosch Frank (2):
>>> s390x: Add CR save area
>>> s390x: Remove DAT and add short indication psw bits on diag308 reset
>>>
>>> lib/s390x/asm-offsets.c | 3 ++-
>>> lib/s390x/asm/arch_def.h | 5 +++--
>>> lib/s390x/interrupt.c | 4 ++--
>>> lib/s390x/smp.c | 2 +-
>>> s390x/cstart64.S | 29 ++++++++++++++++++++---------
>>> 5 files changed, 28 insertions(+), 15 deletions(-)
>>>
>>> --
>>> 2.20.1
>>>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2019-11-05 18:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-05 16:28 [kvm-unit-tests PATCH 0/2] s390x: Improve architectural compliance for diag308 Janosch Frank
2019-11-05 16:28 ` [kvm-unit-tests PATCH 1/2] s390x: Add CR save area Janosch Frank
2019-11-05 19:33 ` David Hildenbrand
2019-11-05 16:28 ` [kvm-unit-tests PATCH 2/2] s390x: Remove DAT and add short indication psw bits on diag308 reset Janosch Frank
2019-11-05 19:53 ` David Hildenbrand
2019-11-06 6:58 ` Janosch Frank
2019-11-06 10:19 ` Janosch Frank
2019-11-05 17:34 ` [kvm-unit-tests PATCH 0/2] s390x: Improve architectural compliance for diag308 David Hildenbrand
2019-11-05 18:23 ` Christian Borntraeger
2019-11-05 18:37 ` Janosch Frank [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=2cb61837-dc0e-2b9f-cf40-1abb430af404@linux.ibm.com \
--to=frankja@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=david@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--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