From: Janosch Frank <frankja@linux.ibm.com>
To: Collin Walling <walling@linux.ibm.com>,
pbonzini@redhat.com, david@redhat.com, cohuck@redhat.com,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-s390@vger.kernel.org
Cc: schwidefsky@de.ibm.com, heiko.carstens@de.ibm.com,
borntraeger@de.ibm.com
Subject: Re: [PATCH v3 1/2] s390/setup: diag318: remove bit check and refactor struct
Date: Wed, 3 Apr 2019 08:36:28 +0200 [thread overview]
Message-ID: <39632665-8861-a386-a1c9-9ce9d081f868@linux.ibm.com> (raw)
In-Reply-To: <20190402174636.15175-2-walling@linux.ibm.com>
[-- Attachment #1.1: Type: text/plain, Size: 1111 bytes --]
On 02.04.19 19:46, Collin Walling wrote:
> Execution of DIAGNOSE 0x318 is fenced by checking an SCLP bit
> for the availability of hardware support for the instruction.
>
> In order to support this instruction for a KVM/QEMU guest, we
> would need to provide modifications to the SCLP Read SCP Info
> data, which will in turn reduce the maximum number of CPUs that
> may be provided to the guest. This issue introduces compatability
> and legacy concerns.
s/compatability/compatibility/
>
> Let's circumvent this issue by removing the bit check and blindly
> executing the instruction. An exception table rule is in place to
> catch the case where hardware does not support this instruction.
Great, another ESSA like instruction...
The sclp bit is still there but we can choose to ignore it for a spec
exception.
>
> While we're at it, let's condense the version code fields in the
> diag318_info struct until we can determine how it will be used.
>
> This modifies commit 4ad78b8651aacf26b3ab6d1e784952eb70469c43
>
> Signed-off-by: Collin Walling <walling@linux.ibm.com>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2019-04-03 6:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-02 17:46 [PATCH v3 0/2] Use DIAG318 to set Control Program Name & Version Codes Collin Walling
2019-04-02 17:46 ` [PATCH v3 1/2] s390/setup: diag318: remove bit check and refactor struct Collin Walling
2019-04-03 6:36 ` Janosch Frank [this message]
2019-04-03 11:28 ` Christian Borntraeger
2019-04-03 12:09 ` David Hildenbrand
2019-04-03 12:10 ` Christian Borntraeger
2019-04-03 12:03 ` David Hildenbrand
2019-04-03 12:33 ` Cornelia Huck
2019-04-03 14:22 ` Collin Walling
2019-04-02 17:46 ` [PATCH v3 2/2] s390/kvm: diagnose 318 handling Collin Walling
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=39632665-8861-a386-a1c9-9ce9d081f868@linux.ibm.com \
--to=frankja@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=schwidefsky@de.ibm.com \
--cc=walling@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).