From: Sebastian Ott <sebott@linux.ibm.com>
To: Tony Krowiak <akrowiak@linux.ibm.com>
Cc: linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org,
freude@de.ibm.com, borntraeger@de.ibm.com, cohuck@redhat.com,
pmorel@linux.vnet.ibm.com, pasic@linux.vnet.ibm.com,
akrowiak@linux.vnet.ibm.com, oberpar@linux.ibm.com
Subject: Re: [PATCH v3] zcrypt: handle AP Info notification from CHSC SEI command
Date: Mon, 11 Mar 2019 16:57:00 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.2.21.1903111656170.8196@schleppi> (raw)
In-Reply-To: <9224eca6-6d2c-7089-1fb2-618a04d7286b@linux.ibm.com>
On Mon, 11 Mar 2019, Tony Krowiak wrote:
> On 2/18/19 12:01 PM, Tony Krowiak wrote:
> > The current AP bus implementation periodically polls the AP configuration
> > to detect changes. When the AP configuration is dynamically changed via the
> > SE or an SCLP instruction, the changes will not be reflected to sysfs until
> > the next time the AP configuration is polled. The CHSC architecture
> > provides a Store Event Information (SEI) command to make notification of an
> > AP configuration change. This patch introduces a handler to process
> > notification from the CHSC SEI command by immediately kicking off an AP bus
> > scan-after-event.
>
> Ping
Applied.
next prev parent reply other threads:[~2019-03-11 15:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-18 17:01 [PATCH v3] zcrypt: handle AP Info notification from CHSC SEI command Tony Krowiak
2019-02-21 16:19 ` Tony Krowiak
2019-03-11 14:28 ` Tony Krowiak
2019-03-11 15:57 ` Sebastian Ott [this message]
2019-03-12 15:02 ` Tony Krowiak
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=alpine.LFD.2.21.1903111656170.8196@schleppi \
--to=sebott@linux.ibm.com \
--cc=akrowiak@linux.ibm.com \
--cc=akrowiak@linux.vnet.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=freude@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=oberpar@linux.ibm.com \
--cc=pasic@linux.vnet.ibm.com \
--cc=pmorel@linux.vnet.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