All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 3/4] qdev: very first cut of scsi bus support.
Date: Fri, 12 Jun 2009 16:58:43 +0200	[thread overview]
Message-ID: <4A326D23.4070401@redhat.com> (raw)
In-Reply-To: <200906121222.46360.paul@codesourcery.com>

On 06/12/09 13:22, Paul Brook wrote:
> On Friday 12 June 2009, Gerd Hoffmann wrote:
>> +
>> +    if (bus) {
>> +        d = scsi_create_simple(bus, "scsi-disk");
>> +    } else {
>> +        /* temporary until usb is qdev-ified */
>> +        d = (SCSIDevice *)qemu_mallocz(sizeof(SCSIDevice));
>
>> +static void scsi_disk_initfn(SCSIDevice *dev)
>> +{
>> +    /* TODO */
>> +}
>
> These are both fairly good indicators that this patch is nowhere near ready
> for integration. The whole point of the qdev API is to abstract device
> creation from individual device implementation details.

I know.  It is tagged "very first cut" for a reason ;)
Just skip it for now if you prefer to wait for something more complete.

> Your implementation
> has the abstraction layers completely backwards.

Yes, but this is how it works in qemu today.
Changing that without breaking stuff isn't that easy though.
Guess I'll first have a look at usb anyway, so I can make sure 
usb-storage is covered too.

cheers,
   Gerd

  reply	other threads:[~2009-06-12 15:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-12  9:28 [Qemu-devel] [PATCH 0/4] qdev patches Gerd Hoffmann
2009-06-12  9:28 ` [Qemu-devel] [PATCH 1/4] qdev: update pci device registration Gerd Hoffmann
2009-06-12  9:28 ` [Qemu-devel] [PATCH 2/4] qdev: replace bus_type enum with bus_info struct Gerd Hoffmann
2009-06-12  9:28 ` [Qemu-devel] [PATCH 3/4] qdev: very first cut of scsi bus support Gerd Hoffmann
2009-06-12 11:22   ` Paul Brook
2009-06-12 14:58     ` Gerd Hoffmann [this message]
2009-06-12  9:28 ` [Qemu-devel] [PATCH 4/4] qdev: hook up i440fx Gerd Hoffmann

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=4A326D23.4070401@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.