From: Cornelia Huck <cohuck@redhat.com>
To: Matthew Rosato <mjrosato@linux.ibm.com>,
Jared Rossi <jrossi@linux.ibm.com>,
Eric Farman <farman@linux.ibm.com>,
Halil Pasic <pasic@linux.ibm.com>
Cc: qemu-s390x@nongnu.org, qemu-devel@nongnu.org, mkawano@linux.ibm.com
Subject: Re: [PATCH v2 0/2] s390x: improve subchannel error handling (vfio)
Date: Mon, 09 Aug 2021 13:15:34 +0200 [thread overview]
Message-ID: <87czqmyill.fsf@redhat.com> (raw)
In-Reply-To: <409ce925-d040-68a6-2d50-f144a1807f2a@linux.ibm.com>
On Wed, Aug 04 2021, Matthew Rosato <mjrosato@linux.ibm.com> wrote:
> On 8/4/21 8:30 PM, Jared Rossi wrote:
>> I've exercised the error paths and it appears to all work correctly.
>>
>> On 7/19/21 11:09 AM, Jared Rossi wrote:
>>> I will take a look and see if I can exercise the error paths.
>>>
>>> Regards,
>>>
>>> Jared Rossi
>
> Thanks Jared! So, with that I'd suggest a
>
> Tested-by: Jared Rossi <jrossi@linux.ibm.com>
I took the liberty to include that.
>
> and as I said earlier the code LGTM -- so for the series:
>
> Reviewed-by: Matthew Rosato <mjrosato@linux.ibm.com>
Thanks to you both!
>
>>>
>>> On 7/19/21 10:16 AM, Matthew Rosato wrote:
>>>> On 7/5/21 12:39 PM, Cornelia Huck wrote:
>>>>> This is a followup on the first version (which I had sent out in May,
>>>>> and which kind of fell through the cracks.) While the first patch
>>>>> is mostly unchanged, I added a second patch to address some possible
>>>>> problems with the generated unit exceptions; non-vfio subchannels
>>>>> are not affected by this.
>>>>>
>>>>> As before, this works on the good path, and I have not managed to
>>>>> actually get my system to exercise the error path :(
>>>>
>>>> Sorry for the silence, was out of office for a bit and Eric is
>>>> unavailable -- Anyway the code LGTM and matches what I see in the
>>>> POPs, I'd be willing to ACK but I'd feel better if we could exercise
>>>> the error paths before merging.
>>>>
>>>> @Jared/@Mike, you've both had eyes on this area of code recently,
>>>> would one of you be willing to take a crack at a tested-by (non-zero
>>>> CCs on HSCH/CSCH + also drive the sch_gen_unit_exception path)?
>>>>
>>>>>
>>>>> v1->v2:
>>>>> - add comments regarding -ENODEV/-EACCES handling
>>>>> - add second patch
>>>>>
>>>>> Cornelia Huck (2):
>>>>> vfio-ccw: forward halt/clear errors
>>>>> css: fix actl handling for unit exceptions
>>>>>
>>>>> hw/s390x/css.c | 38 ++++++++++++++++++++++++++++++++++----
>>>>> hw/vfio/ccw.c | 4 ++--
>>>>> include/hw/s390x/css.h | 3 ++-
>>>>> 3 files changed, 38 insertions(+), 7 deletions(-)
>>>>>
>>>>
Queued to s390-next.
prev parent reply other threads:[~2021-08-09 11:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-05 16:39 [PATCH v2 0/2] s390x: improve subchannel error handling (vfio) Cornelia Huck
2021-07-05 16:39 ` [PATCH v2 1/2] vfio-ccw: forward halt/clear errors Cornelia Huck
2021-07-05 16:39 ` [PATCH v2 2/2] css: fix actl handling for unit exceptions Cornelia Huck
2021-07-19 14:16 ` [PATCH v2 0/2] s390x: improve subchannel error handling (vfio) Matthew Rosato
2021-07-19 15:09 ` Jared Rossi
2021-08-05 0:30 ` Jared Rossi
2021-08-05 1:21 ` Matthew Rosato
2021-08-09 11:15 ` Cornelia Huck [this message]
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=87czqmyill.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=farman@linux.ibm.com \
--cc=jrossi@linux.ibm.com \
--cc=mjrosato@linux.ibm.com \
--cc=mkawano@linux.ibm.com \
--cc=pasic@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).