From: Andi Kleen <ak@muc.de>
To: Christopher Li <chrisl@vmware.com>
Cc: linux-usb-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: compat ioctl for submiting URB
Date: Sat, 29 Jan 2005 07:33:31 +0100 [thread overview]
Message-ID: <m1llaclp6s.fsf@muc.de> (raw)
In-Reply-To: <20050128212304.GA11024@64m.dyndns.org> (Christopher Li's message of "Fri, 28 Jan 2005 16:23:04 -0500")
Christopher Li <chrisl@vmware.com> writes:
> VMware is a big user of the usbdevfs, we translate guest USB
> IO to usbdevfs, by submitting URB. On the x86_64 system, we
> need those compatible ioctl for submitting URBs. For now we
> make a hack to submit it through the vmmon driver. But that
> is very ugly.
>
> I do want this problem get fixed in the linux kernel eventually.
> I have been toying with two different ways to solve it. It seems
> that it is unavoidable to get hands dirty in the usbdevfs internals.
> The first one is just educate the usbdevfs to know about the 32 bit
> URB ioctls. So it don't need to keep around a bounce buffer.
Looks reasonable from a first look.
Issues:
- Should use CONFIG_COMPAT, not x86-64 specific symbols
- Why can't you set URB_COMPAT transparently in the emulation
layer? Then existing applications would hopefully work without
changes, right?
You may also want to preserve the __user casts, otherwise
Al Viro and other sparse users will be unhappy.
Thanks for attacking this long standing problem.
-Andi
next prev parent reply other threads:[~2005-01-29 6:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-28 21:23 compat ioctl for submiting URB Christopher Li
2005-01-29 4:29 ` Gianni Tedesco
2005-01-29 1:33 ` Christopher Li
2005-01-29 5:45 ` Roland Dreier
2005-01-29 4:30 ` Christopher Li
2005-01-29 5:47 ` Al Viro
2005-01-29 6:28 ` Andi Kleen
2005-01-29 6:33 ` Andi Kleen [this message]
2005-01-29 4:55 ` Christopher Li
2005-01-29 5:58 ` [PATCH] compat USB ioctl take II was " Christopher Li
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=m1llaclp6s.fsf@muc.de \
--to=ak@muc.de \
--cc=chrisl@vmware.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
/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