qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Juergen Gross <jgross@suse.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: xen-devel@lists.xensource.com, qemu-devel@nongnu.org,
	stefano.stabellini@eu.citrix.com
Subject: Re: [Qemu-devel] [Patch V1 2/3] xen/usb: add capability for passing through isoc jobs to host devices
Date: Wed, 9 Sep 2015 15:10:11 +0200	[thread overview]
Message-ID: <55F02FB3.6060607@suse.com> (raw)
In-Reply-To: <1441800060.27149.50.camel@redhat.com>

On 09/09/2015 02:01 PM, Gerd Hoffmann wrote:
>    Hi,
>
>>> So, the signaling needs to be different.  The host adapter needs to
>>> signal somehow that it can handle async iso packets.  One way would be
>>> to flag this per usb bus, another one per usb packet.  Also all xen
>>> naming and the xen inlude should go away.  BTW: does this build without
>>> xen-devel installed?
>>
>> Okay, I'll try to make it more generic. I think the async iso capability
>> should be a bus attribute.
>
> Makes sense.
>
>>> Can we get rid of the callbacks?  By filling the USBPacket iovec with
>>> the iso request chunks for example?
>>
>> Difficult. One iso request chunk could require multiple iovec entries.
>
> Why multiple small iovecs instead of one big iovec?

The guest buffer might span multiple physical non contiguous pages. I
don't want to copy data to a new buffer due to performance reasons
(there is already at least one copy operation done by qemu).

> usb_host_req_complete_iso_xen() returns a single status for the whole
> USBPacket anyway ...

I need status per iso request, and libusb does deliver that.

>> The RFC version tried to avoid the callbacks and there you didn't like
>> exposing the additional structures.
>
> -ENOPATCH.

Aah, sorry, my fault. I think this was part of the off-list discussion
we had.


Juergen

  reply	other threads:[~2015-09-09 13:10 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-03 10:45 [Qemu-devel] [Patch V1 0/3] usb, xen: add pvUSB backend Juergen Gross
2015-09-03 10:45 ` [Qemu-devel] [Patch V1 1/3] xen: introduce dummy system device Juergen Gross
2015-09-07 15:29   ` Stefano Stabellini
2015-09-09 11:01     ` [Qemu-devel] [Xen-devel] " Juergen Gross
2015-09-03 10:45 ` [Qemu-devel] [Patch V1 2/3] xen/usb: add capability for passing through isoc jobs to host devices Juergen Gross
2015-09-04 13:25   ` Gerd Hoffmann
2015-09-09 11:37     ` Juergen Gross
2015-09-09 12:01       ` Gerd Hoffmann
2015-09-09 13:10         ` Juergen Gross [this message]
2015-09-09 14:43           ` Gerd Hoffmann
2015-09-15 19:17   ` [Qemu-devel] [Xen-devel] " Konrad Rzeszutek Wilk
2015-09-03 10:45 ` [Qemu-devel] [Patch V1 3/3] xen: add pvUSB backend Juergen Gross
2015-09-07 17:38   ` Stefano Stabellini
2015-09-09 11:22     ` [Qemu-devel] [Xen-devel] " Juergen Gross
2015-09-09 13:13       ` Stefano Stabellini
2015-10-27 18:54   ` Konrad Rzeszutek Wilk
2016-03-07 12:43     ` Juergen Gross

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=55F02FB3.6060607@suse.com \
    --to=jgross@suse.com \
    --cc=kraxel@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xensource.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;
as well as URLs for NNTP newsgroup(s).