qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Janosch Frank <frankja@linux.ibm.com>
To: David Hildenbrand <david@redhat.com>, qemu-devel@nongnu.org
Cc: borntraeger@de.ibm.com, cohuck@redhat.com,
	Richard Henderson <richard.henderson@linaro.org>
Subject: Re: [PATCH] s390x: Properly fetch and test the short psw on diag308 subc 0/1
Date: Mon, 11 Nov 2019 14:52:18 +0100	[thread overview]
Message-ID: <99a1b443-1bf5-e21b-dcdd-6feafd6d9b6f@linux.ibm.com> (raw)
In-Reply-To: <f62ecfe8-970c-bd53-aec1-7cc18b987f19@redhat.com>


[-- Attachment #1.1: Type: text/plain, Size: 1063 bytes --]

On 11/5/19 9:07 PM, David Hildenbrand wrote:
> On 05.11.19 20:34, Janosch Frank wrote:
>> On 11/5/19 8:29 PM, David Hildenbrand wrote:
>>> On 05.11.19 19:44, Janosch Frank wrote:
[...]
> Note: For TCG we miss many of these validity checks. For KVM, most 
> should be triggered when running the VCPU AFAIK (that means, we don't 
> have to check for any other scenarios here). Checking for the special 
> case as given in the programming note should be sufficient.
> 
> 
> I'll have to think about how to best handle that for TCG (mazbe what I 
> proposed works). We could ignore TCG for now and add a TODO. Then, just 
> wrap the exception in a "if (kvm_enabled())". You could also document 
> why we only have to check for this very specific bit and not the other 
> bits (handled by HW later).
> 

After some discussion I got an interesting answer:
For KVM we need to expand the short psw and invert bit 12.
The next SIE entry will automatically report a PIC 6.

I'd propose that I'll fix this patch and send a v2 and you can fix TCG :)


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2019-11-11 13:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-05 18:44 [PATCH] s390x: Properly fetch and test the short psw on diag308 subc 0/1 Janosch Frank
2019-11-05 19:29 ` David Hildenbrand
2019-11-05 19:34   ` Janosch Frank
2019-11-05 20:07     ` David Hildenbrand
2019-11-11 13:52       ` Janosch Frank [this message]
2019-11-11 14:09         ` David Hildenbrand

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=99a1b443-1bf5-e21b-dcdd-6feafd6d9b6f@linux.ibm.com \
    --to=frankja@linux.ibm.com \
    --cc=borntraeger@de.ibm.com \
    --cc=cohuck@redhat.com \
    --cc=david@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.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).