From: Eric Farman <farman@linux.ibm.com>
To: Cornelia Huck <cohuck@redhat.com>
Cc: Halil Pasic <pasic@linux.ibm.com>,
Jason Herne <jjherne@linux.ibm.com>,
qemu-s390x@nongnu.org, qemu-devel@nongnu.org,
Jared Rossi <jrossi@linux.ibm.com>
Subject: Re: [RFC PATCH v1 2/8] vfio-ccw: Don't inject an I/O interrupt if the subchannel is not enabled
Date: Tue, 19 Nov 2019 10:47:53 -0500 [thread overview]
Message-ID: <413cff23-0116-3862-616b-be39eddceadc@linux.ibm.com> (raw)
In-Reply-To: <20191118192310.6af29cd1.cohuck@redhat.com>
On 11/18/19 1:23 PM, Cornelia Huck wrote:
> On Fri, 15 Nov 2019 04:34:31 +0100
> Eric Farman <farman@linux.ibm.com> wrote:
>
>> From: Farhan Ali <alifm@linux.ibm.com>
>>
>> According to PoPs, when the SCHIB.PMCW bit 8 is 0 status presented by
>> the device is not made available to the program. So don't inject an
>> interrupt in the guest if the guest OS has not enabled the
>> subchannel.
>
> Have you managed to trigger this state in real life?
No, and I have no notes on how this came to be. I'll try running some
of the config tests with this reverted, and see if I can find any weirdness.
>
>>
>> Signed-off-by: Farhan Ali <alifm@linux.ibm.com>
>> Signed-off-by: Eric Farman <farman@linux.ibm.com>
>> ---
>>
>> Notes:
>> v0->v1: [EF]
>> - Update commit message, as the bit in question is bit 8 not 15
>>
>> hw/vfio/ccw.c | 5 +++++
>> 1 file changed, 5 insertions(+)
>>
>> diff --git a/hw/vfio/ccw.c b/hw/vfio/ccw.c
>> index 0919ddbeb8..0590a6f512 100644
>> --- a/hw/vfio/ccw.c
>> +++ b/hw/vfio/ccw.c
>> @@ -230,6 +230,11 @@ static void vfio_ccw_io_notifier_handler(void *opaque)
>> return;
>> }
>>
>> + /* Virtual subchannel is not enabled */
>> + if (!(schib->pmcw.flags & PMCW_FLAGS_MASK_ENA)) {
>
> How can that happen? We should not be able to disable the subchannel
> while it is in active use, should we? I fear I'm missing something
> here...
Me too... Hrm...
>
>> + return;
>> + }
>> +
>> size = pread(vcdev->vdev.fd, region, vcdev->io_region_size,
>> vcdev->io_region_offset);
>> if (size == -1) {
>
next prev parent reply other threads:[~2019-11-19 15:49 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-15 3:34 [RFC PATCH v1 0/8] s390x/vfio-ccw: Channel Path Handling Eric Farman
2019-11-15 3:34 ` [RFC PATCH v1 1/8] vfio-ccw: Return IOINST_CC_NOT_OPERATIONAL for EIO Eric Farman
2019-11-18 18:13 ` Cornelia Huck
2019-11-19 11:23 ` Halil Pasic
2019-11-19 12:02 ` Cornelia Huck
2019-11-19 15:42 ` Eric Farman
2019-11-19 17:59 ` Halil Pasic
2019-11-20 10:11 ` Cornelia Huck
2019-11-19 15:49 ` Eric Farman
2019-11-15 3:34 ` [RFC PATCH v1 2/8] vfio-ccw: Don't inject an I/O interrupt if the subchannel is not enabled Eric Farman
2019-11-18 18:23 ` Cornelia Huck
2019-11-19 15:47 ` Eric Farman [this message]
2019-11-15 3:34 ` [RFC PATCH v1 3/8] linux-headers: update Eric Farman
2019-11-15 3:34 ` [RFC PATCH v1 4/8] vfio-ccw: Refactor cleanup of regions Eric Farman
2019-11-20 10:31 ` Cornelia Huck
2019-11-15 3:34 ` [RFC PATCH v1 5/8] vfio-ccw: Add support for the schib region Eric Farman
2019-11-20 11:13 ` Cornelia Huck
2020-01-31 20:15 ` Eric Farman
2020-02-03 10:43 ` Cornelia Huck
2019-11-15 3:34 ` [RFC PATCH v1 6/8] vfio-ccw: Add support for the crw region Eric Farman
2019-11-20 12:30 ` Cornelia Huck
2019-11-15 3:34 ` [RFC PATCH v1 7/8] vfio-ccw: Refactor ccw irq handler Eric Farman
2019-11-20 12:39 ` Cornelia Huck
2019-12-03 20:01 ` Eric Farman
2019-11-15 3:34 ` [RFC PATCH v1 8/8] vfio-ccw: Add support for the CRW irq Eric Farman
2019-11-20 12:50 ` 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=413cff23-0116-3862-616b-be39eddceadc@linux.ibm.com \
--to=farman@linux.ibm.com \
--cc=cohuck@redhat.com \
--cc=jjherne@linux.ibm.com \
--cc=jrossi@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 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.