qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Yanqiangjun <yanqiangjun@huawei.com>,
	Hanweidong <hanweidong@huawei.com>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	Luonengjun <luonengjun@huawei.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"hdegoede@redhat.com" <hdegoede@redhat.com>,
	"Gonglei (Arei)" <arei.gonglei@huawei.com>
Subject: Re: [Qemu-devel] USB2.0 disk format failure in windows guest
Date: Tue, 16 Apr 2013 17:38:42 +0200	[thread overview]
Message-ID: <516D7082.9090101@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1304161048280.1391-100000@iolanthe.rowland.org>

  Hi,

> Fixing this will require qemu to copy the beginning and ending parts of
> these non-aligned qTDs into separate bounce buffers so that the URB
> length can be divisible by 512.

Worth trying:  http://www.kraxel.org/cgit/qemu/log/?h=usb.80

It puts the qemu usb passthrough code upside down.  All xfers will go
through a bounce buffer, requests are submitted via libusbx.  That
should fix it.  Of course there is the risk of regressions in other
areas as it is all new code.  Also make sure you have libusbx-devel
installed, otherwise qemu will fallback to the old code which uses usbfs
ioctls directly.

cheers,
  Gerd

  reply	other threads:[~2013-04-16 15:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <33183CC9F5247A488A2544077AF190203862EE48@szxeml538-mbx.china.huawei.com>
     [not found] ` <Pine.LNX.4.44L0.1304111202251.943-100000@iolanthe.rowland.org>
2013-04-14  4:09   ` [Qemu-devel] USB2.0 disk format failure in windows guest Gonglei (Arei)
2013-04-15 17:43     ` Alan Stern
2013-04-16  3:40       ` Gonglei (Arei)
2013-04-16 15:20         ` Alan Stern
2013-04-16 15:38           ` Gerd Hoffmann [this message]
2013-04-17 11:15             ` Gonglei (Arei)
2013-04-17 10:55           ` Gonglei (Arei)
2013-03-21  7:43 Gonglei (Arei)

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=516D7082.9090101@redhat.com \
    --to=kraxel@redhat.com \
    --cc=arei.gonglei@huawei.com \
    --cc=hanweidong@huawei.com \
    --cc=hdegoede@redhat.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=luonengjun@huawei.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stern@rowland.harvard.edu \
    --cc=yanqiangjun@huawei.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).