From: Gerd Hoffmann <kraxel@redhat.com>
To: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] qdev: very first cut of scsi bus support.
Date: Thu, 11 Jun 2009 16:39:34 +0200 [thread overview]
Message-ID: <4A311726.10003@redhat.com> (raw)
In-Reply-To: <200906111308.59756.paul@codesourcery.com>
On 06/11/09 14:08, Paul Brook wrote:
>> Signed-off-by: Gerd Hoffmann<kraxel@redhat.com>
>
> I think you need to figure out how this interacts with scsi devices that are
> not attached to a parallel scsi interface (e.g. usb mass storage).
Yes, noticed that too. Didn't investigate yet due to usb knowing
nothing about qdev yet.
> The current qemu scsi api exposes individual devices. The actual bus emulation
> is contained within the host adapter. My guess is that you may need an
> additional layer to separate the parallel scsi bus from actual scsi devices.
And the guest <-> host (block) device linking needs a solution too.
cheers,
Gerd
prev parent reply other threads:[~2009-06-11 14:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-10 13:59 [Qemu-devel] [PATCH] qdev: very first cut of scsi bus support Gerd Hoffmann
2009-06-11 12:08 ` Paul Brook
2009-06-11 14:39 ` Gerd Hoffmann [this message]
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=4A311726.10003@redhat.com \
--to=kraxel@redhat.com \
--cc=paul@codesourcery.com \
--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).