qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>,
	Janosch Frank <frankja@linux.ibm.com>,
	qemu-devel@nongnu.org
Cc: qemu-s390x@nongnu.org, cohuck@redhat.com
Subject: Re: [PATCH] s390x: pv: Fence additional unavailable SCLP facilities for PV guests
Date: Tue, 8 Dec 2020 17:19:48 +0100	[thread overview]
Message-ID: <e22f4e78-c996-ed3d-0680-7c33bd480d83@redhat.com> (raw)
In-Reply-To: <66975842-fcf3-013d-9bba-fed5c2c69a67@de.ibm.com>

On 08.12.20 17:11, Christian Borntraeger wrote:
> 
> 
> On 08.12.20 15:55, David Hildenbrand wrote:
>> On 08.12.20 14:29, Christian Borntraeger wrote:
>>>
>>>
>>> On 04.12.20 09:36, Janosch Frank wrote:
>>>> There's no VSIE support for a protected guest, so let's better not
>>>> advertise it and its support facilities.
>>>>
>>>> Signed-off-by: Janosch Frank <frankja@linux.ibm.com>
>>>
>>> Looks sane. Assuming that all features that depend on SIE are named S390_FEAT_SIE_*
>>> this should take care of everything. (i compared to gen-facilities.c)
>>
>> We could add dependency checks to
>> target/s390x/cpu_models.c:check_consistency()
> 
> That could be an additional patch, right?

Yeah sure.

> 
>>
>> What about
>>
>> DEF_FEAT(ESOP, "esop", SCLP_CONF_CHAR, 46,
>> "Enhanced-suppression-on-protection facility")
> 
> ESOP does make sense independent from SIE see chapter 3-15 in the POP
> in "Suppression on Protection"
> 

Rings a bell :)

> 
>> DEF_FEAT(HPMA2, "hpma2", SCLP_CONF_CHAR, 90, "Host page management
>> assist 2 Facility")
> 
> Right. We should also fence of hpma2.

I was also wondering about CMM, but as the guest senses it by executing
the instruction, protected guests will never see it I assume.

-- 
Thanks,

David / dhildenb



  reply	other threads:[~2020-12-08 16:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-04  8:36 [PATCH] s390x: pv: Fence additional unavailable SCLP facilities for PV guests Janosch Frank
2020-12-08 13:29 ` Christian Borntraeger
2020-12-08 14:55   ` David Hildenbrand
2020-12-08 16:11     ` Christian Borntraeger
2020-12-08 16:19       ` David Hildenbrand [this message]
2020-12-09  8:54         ` Janosch Frank

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=e22f4e78-c996-ed3d-0680-7c33bd480d83@redhat.com \
    --to=david@redhat.com \
    --cc=borntraeger@de.ibm.com \
    --cc=cohuck@redhat.com \
    --cc=frankja@linux.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-s390x@nongnu.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).