From: Cornelia Huck <cohuck@redhat.com>
To: David Hildenbrand <david@redhat.com>
Cc: Christian Borntraeger <borntraeger@de.ibm.com>,
qemu-devel <qemu-devel@nongnu.org>,
qemu-s390x <qemu-s390x@nongnu.org>,
Halil Pasic <pasic@linux.ibm.com>,
Richard Henderson <rth@twiddle.net>,
Collin Walling <walling@linux.ibm.com>,
"Jason J . Herne" <jjherne@linux.ibm.com>
Subject: Re: [Qemu-devel] [PATCH v3 4/9] s390x/cpumodel: msa9 facility
Date: Tue, 30 Apr 2019 09:13:54 +0200 [thread overview]
Message-ID: <20190430091354.23c9aca0.cohuck@redhat.com> (raw)
In-Reply-To: <6e6c4b4e-4d08-b4fa-1092-06567a6473da@redhat.com>
On Tue, 30 Apr 2019 09:00:56 +0200
David Hildenbrand <david@redhat.com> wrote:
> On 30.04.19 07:41, Christian Borntraeger wrote:
> >
> >
> > On 29.04.19 21:24, David Hildenbrand wrote:
> >> Just wondering, why keep the PCKMO ones separate, but not e.g. PCC ?
> >
> > Because those can be disabled at the HMC. It is painful to disable 5 elements
> > for LPARs that are configured that way. So I created a group for those. That
> > will allow to disable the full group.
> > (we have the same issue with the exisiting AES and DEA pckmo functions).
>
> Rings a bell, maybe that information would be good to have in the cover
> letter. I guess Conny might want to change the description when picking up:
>
> "Provide the MSA9 facility (stfle.155). This also contains pckmo
> subfunctions for key wrapping. Keep them in a separate group to disable
> those as a block if necessary. This is for example needed when disabling
> key wrapping via the HMC."
Sure, makes sense to fold that in.
WARNING: multiple messages have this Message-ID (diff)
From: Cornelia Huck <cohuck@redhat.com>
To: David Hildenbrand <david@redhat.com>
Cc: "Jason J . Herne" <jjherne@linux.ibm.com>,
Collin Walling <walling@linux.ibm.com>,
qemu-devel <qemu-devel@nongnu.org>,
Halil Pasic <pasic@linux.ibm.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
qemu-s390x <qemu-s390x@nongnu.org>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH v3 4/9] s390x/cpumodel: msa9 facility
Date: Tue, 30 Apr 2019 09:13:54 +0200 [thread overview]
Message-ID: <20190430091354.23c9aca0.cohuck@redhat.com> (raw)
Message-ID: <20190430071354.l_Gzgx6i2XSiKmWLOaoV-iwX07wuT7xOBYAjhpupDss@z> (raw)
In-Reply-To: <6e6c4b4e-4d08-b4fa-1092-06567a6473da@redhat.com>
On Tue, 30 Apr 2019 09:00:56 +0200
David Hildenbrand <david@redhat.com> wrote:
> On 30.04.19 07:41, Christian Borntraeger wrote:
> >
> >
> > On 29.04.19 21:24, David Hildenbrand wrote:
> >> Just wondering, why keep the PCKMO ones separate, but not e.g. PCC ?
> >
> > Because those can be disabled at the HMC. It is painful to disable 5 elements
> > for LPARs that are configured that way. So I created a group for those. That
> > will allow to disable the full group.
> > (we have the same issue with the exisiting AES and DEA pckmo functions).
>
> Rings a bell, maybe that information would be good to have in the cover
> letter. I guess Conny might want to change the description when picking up:
>
> "Provide the MSA9 facility (stfle.155). This also contains pckmo
> subfunctions for key wrapping. Keep them in a separate group to disable
> those as a block if necessary. This is for example needed when disabling
> key wrapping via the HMC."
Sure, makes sense to fold that in.
next prev parent reply other threads:[~2019-04-30 7:14 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-29 9:02 [Qemu-devel] [PATCH v3 0/9] s390x: new guest features Christian Borntraeger
2019-04-29 9:02 ` Christian Borntraeger
2019-04-29 9:02 ` [Qemu-devel] [PATCH v3 1/9] linux header sync Christian Borntraeger
2019-04-29 9:02 ` Christian Borntraeger
2019-04-29 9:02 ` [Qemu-devel] [PATCH v3 2/9] s390x/cpumodel: ignore csske for expansion Christian Borntraeger
2019-04-29 9:02 ` Christian Borntraeger
2019-04-29 9:02 ` [Qemu-devel] [PATCH v3 3/9] s390x/cpumodel: Miscellaneous-Instruction-Extensions Facility 3 Christian Borntraeger
2019-04-29 9:02 ` Christian Borntraeger
2019-04-29 9:02 ` [Qemu-devel] [PATCH v3 4/9] s390x/cpumodel: msa9 facility Christian Borntraeger
2019-04-29 9:02 ` Christian Borntraeger
2019-04-29 19:24 ` David Hildenbrand
2019-04-29 19:24 ` David Hildenbrand
2019-04-30 5:41 ` Christian Borntraeger
2019-04-30 5:41 ` Christian Borntraeger
2019-04-30 7:00 ` David Hildenbrand
2019-04-30 7:00 ` David Hildenbrand
2019-04-30 7:13 ` Cornelia Huck [this message]
2019-04-30 7:13 ` Cornelia Huck
2019-04-29 9:02 ` [Qemu-devel] [PATCH v3 5/9] s390x/cpumodel: vector enhancements Christian Borntraeger
2019-04-29 9:02 ` Christian Borntraeger
2019-04-29 9:02 ` [Qemu-devel] [PATCH v3 6/9] s390x/cpumodel: enhanced sort facility Christian Borntraeger
2019-04-29 9:02 ` Christian Borntraeger
2019-04-29 9:02 ` [Qemu-devel] [PATCH v3 7/9] s390x/cpumodel: add Deflate-conversion facility Christian Borntraeger
2019-04-29 9:02 ` Christian Borntraeger
2019-04-29 10:19 ` David Hildenbrand
2019-04-29 10:19 ` David Hildenbrand
2019-04-29 9:02 ` [Qemu-devel] [PATCH v3 8/9] s390x/cpumodel: add gen15 defintions Christian Borntraeger
2019-04-29 9:02 ` Christian Borntraeger
2019-04-29 10:18 ` David Hildenbrand
2019-04-29 10:18 ` David Hildenbrand
2019-04-29 9:02 ` [Qemu-devel] [PATCH v3 9/9] s390x/cpumodel: wire up 8561 and 8562 as gen15 machines Christian Borntraeger
2019-04-29 9:02 ` Christian Borntraeger
2019-04-29 10:17 ` David Hildenbrand
2019-04-29 10:17 ` David Hildenbrand
2019-04-29 9:25 ` [Qemu-devel] [PATCH v3 0/9] s390x: new guest features no-reply
2019-04-29 9:25 ` no-reply
2019-04-29 9:30 ` no-reply
2019-04-29 9:30 ` no-reply
2019-04-29 9:35 ` no-reply
2019-04-29 9:35 ` no-reply
2019-04-29 9:40 ` no-reply
2019-04-29 9:40 ` no-reply
2019-04-29 10:28 ` no-reply
2019-04-29 10:28 ` no-reply
2019-04-29 16:08 ` Cornelia Huck
2019-04-29 16:08 ` Cornelia Huck
2019-05-07 9:07 ` [Qemu-devel] [qemu-s390x] " Christian Borntraeger
2019-05-07 9:49 ` Cornelia Huck
2019-04-29 19:28 ` [Qemu-devel] " no-reply
2019-04-29 19:28 ` no-reply
2019-05-01 13:33 ` no-reply
2019-05-01 13:33 ` no-reply
2019-05-01 14:04 ` no-reply
2019-05-01 14:04 ` no-reply
2019-05-20 6:42 ` Cornelia Huck
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=20190430091354.23c9aca0.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=david@redhat.com \
--cc=jjherne@linux.ibm.com \
--cc=pasic@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=rth@twiddle.net \
--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).