qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Fabrice Bellard <fabrice@bellard.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu usb-linux.c vl.h hw/esp.c hw/lsi53c895a.c ...
Date: Sat, 12 Aug 2006 14:31:21 +0200	[thread overview]
Message-ID: <44DDCA19.4030903@bellard.org> (raw)
In-Reply-To: <E1GBhvP-0004A7-NM@savannah.gnu.org>

Hi,

OK for the SCSI async support. I am making changes to have a better low 
level handling of CDROMs (both real host CDROMs and emulated ones), but 
I don't know when it will be ready. The changes mostly consists in 
adding a method in the block devices to support packet CD commands.

About async USB, maybe some simplifications are possible. When you have 
a real USB controller, there is always a single current request and you 
don't neep to have provisions to handle several ones (of course more 
complicated host controllers could do that, but it is not useful to 
model it now). Moreover, the devices must reply to the request 
immediately so the request are asynchronous just because it takes a few 
uS to send the data, not because the device blocks (I am not sure it is 
clear for you).

So in QEMU, async USB is not needed in practise for emulated devices. 
For MSD you don't need it for example even if you are using SCSI AIO 
because the host keep polling the MSD storage device until there is an 
SCSI reply.

Async USB is only really needed in the case where QEMU speaks to a host 
device. In this case the operation to send a TD may block (ideally at 
most 1 ms) and it is interesting to hide that to the guest. In this 
case, we must make compromises to hide this fact to the guest. Your 
proposal seems good for that but USB frames will be longer than 1 ms in 
case of host devices (and I am ready to accept that as it is better than 
the previous solution !).

The more complicated implementation would be to suppress USB async as 
you did it but to export to the generic USB layers that list of TD that 
the controller maintains. Then it is possible to submit several requests 
at once to the host devices while having a consistent low level model.

Regards,

Fabrice.

  reply	other threads:[~2006-08-12 12:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-12  1:04 [Qemu-devel] qemu usb-linux.c vl.h hw/esp.c hw/lsi53c895a.c Paul Brook
2006-08-12 12:31 ` Fabrice Bellard [this message]
2006-08-12 14:19   ` Paul Brook
2006-08-15 22:56 ` Igor Kovalenko

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=44DDCA19.4030903@bellard.org \
    --to=fabrice@bellard.org \
    --cc=qemu-devel@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).