From: Cornelia Huck <cohuck@redhat.com>
To: Harald Freudenberger <freude@linux.ibm.com>
Cc: Tony Krowiak <akrowiak@linux.ibm.com>,
linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org,
schwidefsky@de.ibm.com, heiko.carstens@de.ibm.com,
sebott@linux.ibm.com, oberpar@linux.ibm.com,
pmorel@linux.ibm.com, pasic@linux.ibm.com
Subject: Re: [PATCH] zcrypt: handle AP Info notification from CHSC SEI command
Date: Mon, 4 Feb 2019 13:07:18 +0100 [thread overview]
Message-ID: <20190204130718.0fb8cdb3.cohuck@redhat.com> (raw)
In-Reply-To: <26ec5e3e-de2c-ad82-825d-d20ba52c8937@linux.ibm.com>
On Mon, 4 Feb 2019 11:15:25 +0100
Harald Freudenberger <freude@linux.ibm.com> wrote:
> On 01.02.19 15:35, Cornelia Huck wrote:
> > On Thu, 31 Jan 2019 18:50:57 -0500
> > Tony Krowiak <akrowiak@linux.ibm.com> wrote:
> >
> >> On 1/31/19 4:55 AM, Cornelia Huck wrote:
> >>> On Wed, 30 Jan 2019 12:48:46 -0500
> >>> Tony Krowiak <akrowiak@linux.ibm.com> wrote:
> >>> Two questions:
> >>> - Does the event cover _any_ change to the AP configuration, or can the
> >>> periodic scan detect changes that are not signaled?
> >> It can detect any change, such as a change to the CRYCB masks.
> > Nice. I suppose we can not rely on those messages being generated,
> > though, and therefore need to keep the periodic scan...
> As you wrote, I am not sure if the ap bus code can rely on this to
> cover all changes. For kvm guests I think it is currently not working
> as there is no such notification generated at all. So I'd like to
> have the periodic scan in place.
Yes, and there are bound to be QEMU versions without that support in
active use even if this is implemented in the future. But a quicker
reaction to changes on real hardware still sounds like a win to me :)
next prev parent reply other threads:[~2019-02-04 12:07 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-30 17:48 [PATCH] zcrypt: handle AP Info notification from CHSC SEI command Tony Krowiak
2019-01-30 18:32 ` Sebastian Ott
2019-01-31 23:28 ` Tony Krowiak
2019-02-01 9:01 ` Heiko Carstens
2019-02-01 11:08 ` Martin Schwidefsky
2019-02-01 13:05 ` Heiko Carstens
2019-02-01 15:40 ` Tony Krowiak
2019-02-01 15:38 ` Tony Krowiak
2019-02-04 10:06 ` Harald Freudenberger
2019-02-05 20:26 ` Tony Krowiak
2019-02-04 10:01 ` Sebastian Ott
2019-02-05 20:27 ` Tony Krowiak
2019-02-21 10:42 ` Harald Freudenberger
2019-02-21 12:12 ` Cornelia Huck
2019-02-21 12:55 ` Heiko Carstens
2019-01-31 9:09 ` Pierre Morel
2019-01-31 23:32 ` Tony Krowiak
2019-01-31 9:23 ` Pierre Morel
2019-01-31 9:55 ` Cornelia Huck
2019-01-31 23:50 ` Tony Krowiak
2019-02-01 14:35 ` Cornelia Huck
2019-02-01 15:50 ` Tony Krowiak
2019-02-04 10:15 ` Harald Freudenberger
2019-02-04 12:07 ` Cornelia Huck [this message]
2019-02-05 20:30 ` Tony Krowiak
2019-02-03 9:25 ` kbuild test robot
2019-02-03 9:25 ` kbuild test robot
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=20190204130718.0fb8cdb3.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=akrowiak@linux.ibm.com \
--cc=freude@linux.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=oberpar@linux.ibm.com \
--cc=pasic@linux.ibm.com \
--cc=pmorel@linux.ibm.com \
--cc=schwidefsky@de.ibm.com \
--cc=sebott@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.