From: Eric Farman <farman@linux.ibm.com>
To: Halil Pasic <pasic@linux.ibm.com>, Cornelia Huck <cohuck@redhat.com>
Cc: Farhan Ali <alifm@linux.ibm.com>,
linux-s390@vger.kernel.org,
Alex Williamson <alex.williamson@redhat.com>,
Pierre Morel <pmorel@linux.ibm.com>,
kvm@vger.kernel.org, qemu-devel@nongnu.org,
qemu-s390x@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v4 1/6] vfio-ccw: make it safe to access channel programs
Date: Thu, 11 Apr 2019 17:27:42 -0400 [thread overview]
Message-ID: <571b9f8c-cfb0-704e-ded4-8661a8136876@linux.ibm.com> (raw)
In-Reply-To: <4a692c11-edb2-93f9-7d8e-96a73a7ecdae@linux.ibm.com>
On 4/10/19 10:59 PM, Eric Farman wrote:
>
>
> On 4/9/19 7:34 PM, Halil Pasic wrote:
>> On Mon, 8 Apr 2019 19:07:47 +0200
...snip...
>> I'm just running fio on a pass-through DASD and on some virto-blk disks
>> in parallel. My QEMU is today's vfio-ccw-caps from your repo.
>>
>> I see stuff like this:
>> qemu-git: vfio-ccw: wirte I/O region failed with errno=16[1811/7332/0
>> iops] [eta 26m:34s]
>
> Without knowing what the I/O was that failed, this is a guessing game.
> But I encountered something similar just now running fio.
>
> qemu:
> 2019-04-11T02:06:09.524838Z qemu-system-s390x: vfio-ccw: wirte I/O
> region failed with errno=16
...snip...
> From the associated I/O, I think this is fixed by a series I am nearly
> ready to send for review. I'll try again with those fixes on top of the
> two series here, and report back.
So, I've run enough combinations to feel comfortable saying that the
error (EBUSY) I saw last night (and presumably the one Halil saw) exists
in today's code and is not introduced by this series. It also appears
to be addressed by one of the patches in a series I'm working on, but
which that series still has some further problems. Sigh, there are too
many branches and too many interrupts.
- Eric
WARNING: multiple messages have this Message-ID (diff)
From: Eric Farman <farman@linux.ibm.com>
To: Halil Pasic <pasic@linux.ibm.com>, Cornelia Huck <cohuck@redhat.com>
Cc: linux-s390@vger.kernel.org, Pierre Morel <pmorel@linux.ibm.com>,
kvm@vger.kernel.org, qemu-s390x@nongnu.org,
Farhan Ali <alifm@linux.ibm.com>,
qemu-devel@nongnu.org,
Alex Williamson <alex.williamson@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v4 1/6] vfio-ccw: make it safe to access channel programs
Date: Thu, 11 Apr 2019 17:27:42 -0400 [thread overview]
Message-ID: <571b9f8c-cfb0-704e-ded4-8661a8136876@linux.ibm.com> (raw)
Message-ID: <20190411212742.bLGON4chEcIy9XHAU7JLBIkMcS_H4FbDQbwweyfKEFM@z> (raw)
In-Reply-To: <4a692c11-edb2-93f9-7d8e-96a73a7ecdae@linux.ibm.com>
On 4/10/19 10:59 PM, Eric Farman wrote:
>
>
> On 4/9/19 7:34 PM, Halil Pasic wrote:
>> On Mon, 8 Apr 2019 19:07:47 +0200
...snip...
>> I'm just running fio on a pass-through DASD and on some virto-blk disks
>> in parallel. My QEMU is today's vfio-ccw-caps from your repo.
>>
>> I see stuff like this:
>> qemu-git: vfio-ccw: wirte I/O region failed with errno=16[1811/7332/0
>> iops] [eta 26m:34s]
>
> Without knowing what the I/O was that failed, this is a guessing game.
> But I encountered something similar just now running fio.
>
> qemu:
> 2019-04-11T02:06:09.524838Z qemu-system-s390x: vfio-ccw: wirte I/O
> region failed with errno=16
...snip...
> From the associated I/O, I think this is fixed by a series I am nearly
> ready to send for review. I'll try again with those fixes on top of the
> two series here, and report back.
So, I've run enough combinations to feel comfortable saying that the
error (EBUSY) I saw last night (and presumably the one Halil saw) exists
in today's code and is not introduced by this series. It also appears
to be addressed by one of the patches in a series I'm working on, but
which that series still has some further problems. Sigh, there are too
many branches and too many interrupts.
- Eric
next prev parent reply other threads:[~2019-04-11 21:27 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-01 9:38 [Qemu-devel] [PATCH v4 0/6] vfio-ccw: support hsch/csch (kernel part) Cornelia Huck
2019-03-01 9:38 ` [Qemu-devel] [PATCH v4 1/6] vfio-ccw: make it safe to access channel programs Cornelia Huck
2019-04-08 17:02 ` Farhan Ali
2019-04-08 17:02 ` Farhan Ali
2019-04-08 17:07 ` Cornelia Huck
2019-04-08 17:07 ` Cornelia Huck
2019-04-08 17:19 ` Farhan Ali
2019-04-08 17:19 ` Farhan Ali
2019-04-08 20:25 ` Eric Farman
2019-04-08 20:25 ` Eric Farman
2019-04-09 23:34 ` Halil Pasic
2019-04-09 23:34 ` Halil Pasic
2019-04-11 2:59 ` Eric Farman
2019-04-11 2:59 ` Eric Farman
2019-04-11 15:58 ` [Qemu-devel] [qemu-s390x] " Halil Pasic
2019-04-11 15:58 ` Halil Pasic
2019-04-11 16:25 ` Eric Farman
2019-04-11 16:25 ` Eric Farman
2019-04-11 16:36 ` Cornelia Huck
2019-04-11 16:36 ` Cornelia Huck
2019-04-11 18:07 ` Halil Pasic
2019-04-11 18:07 ` Halil Pasic
2019-04-11 21:27 ` Eric Farman [this message]
2019-04-11 21:27 ` [Qemu-devel] " Eric Farman
2019-04-12 8:14 ` Cornelia Huck
2019-04-12 8:14 ` Cornelia Huck
2019-03-01 9:38 ` [Qemu-devel] [PATCH v4 2/6] vfio-ccw: rework ssch state handling Cornelia Huck
2019-03-08 22:18 ` Eric Farman
2019-03-11 9:47 ` Cornelia Huck
2019-03-01 9:38 ` [Qemu-devel] [PATCH v4 3/6] vfio-ccw: protect the I/O region Cornelia Huck
2019-03-01 9:39 ` [Qemu-devel] [PATCH v4 4/6] vfio-ccw: add capabilities chain Cornelia Huck
2019-04-15 14:40 ` Eric Farman
2019-04-15 14:40 ` Eric Farman
2019-04-15 15:24 ` Farhan Ali
2019-04-15 15:24 ` Farhan Ali
2019-03-01 9:39 ` [Qemu-devel] [PATCH v4 5/6] s390/cio: export hsch to modules Cornelia Huck
2019-03-01 9:39 ` [Qemu-devel] [PATCH v4 6/6] vfio-ccw: add handling for async channel instructions Cornelia Huck
2019-04-15 14:56 ` Eric Farman
2019-04-15 14:56 ` Eric Farman
2019-04-15 15:25 ` Farhan Ali
2019-04-15 15:25 ` Farhan Ali
2019-03-07 21:28 ` [Qemu-devel] [PATCH v4 0/6] vfio-ccw: support hsch/csch (kernel part) Eric Farman
2019-04-15 11:51 ` Cornelia Huck
2019-04-15 11:51 ` Cornelia Huck
2019-04-15 16:43 ` Cornelia Huck
2019-04-15 16:43 ` 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=571b9f8c-cfb0-704e-ded4-8661a8136876@linux.ibm.com \
--to=farman@linux.ibm.com \
--cc=alex.williamson@redhat.com \
--cc=alifm@linux.ibm.com \
--cc=cohuck@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=pasic@linux.ibm.com \
--cc=pmorel@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).