From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] Re: [PATCH 0/10] qdev patches.
Date: Fri, 19 Jun 2009 18:51:20 +0100 [thread overview]
Message-ID: <200906191851.21563.paul@codesourcery.com> (raw)
In-Reply-To: <4A3BB5F2.9050701@redhat.com>
On Friday 19 June 2009, Gerd Hoffmann wrote:
> Hi,
>
> > Updated patch queue pushed to qdev.v5. Not posting to avoid spamming the
> > list too much. Online viewable via gitweb here:
> > http://git.et.redhat.com/?p=qemu-kraxel.git;a=shortlog;h=refs/heads/qdev.
> >v5
>
> Todays update pushed to qdev.v6.
> http://git.et.redhat.com/?p=qemu-kraxel.git;a=shortlog;h=refs/heads/qdev.v6
A few comments on specific patches:
* qdev: update pci device registration
I dislike passing an {array,length} pair. Especially when it requires every
user to manually get the right length.
* qdev/core: bus list
I don't seen any good reason for this. In fact I think it is a major step
backwards. A bus is uniquely identified by its name and parent device.
* qdev/pci: misc fixes.
All uses of the second argument to savevm should go away, not introduce new
ones. I'm unconvinced by the dev->name change. If we're using the same value
then why does it exist at all?
* qdev/pci: hook up i440fx
i440fx_init should not exist. c.f. versatile_pci.c
* qdev: update pci device registration
This is exactly the sort of fake conversion that I don't like, because you
still require use of the old hardcoded initialization functions.
Convenience wrappers like smc91c111_init are fine (and will naturally
disappear when we have a machine config), but you shouldn't be poking directly
at device state.
In practice there's no way for the user to have more than one set of IDE
busses, so I don't see much point pretending we allow this. i.e. remove the
hd_table argument altogether and use drive_get_index directly.
* qdev: convert all vga
Likewise, pci_vga_init needs to go away.
* qdev/scsi: add scsi bus support to qdev, convert drivers
This still feels wrong, probably because you're using the same thing for both
a parallel scsi bus, and for devices (usb-msd) that incorporate scsi
functionality directly. The current qemu scsi API is actually a set of point
to point links with individual devices. All the bus emulation is local to the
host controller.
* qdev/usb*
I have not looked at these patches.
next prev parent reply other threads:[~2009-06-19 17:51 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-17 12:59 [Qemu-devel] [PATCH 0/10] qdev patches Gerd Hoffmann
2009-06-17 12:59 ` [Qemu-devel] [PATCH 01/10] qdev: update pci device registration Gerd Hoffmann
2009-06-17 12:59 ` [Qemu-devel] [PATCH 02/10] qdev: replace bus_type enum with bus_info struct Gerd Hoffmann
2009-06-17 12:59 ` [Qemu-devel] [PATCH 03/10] qdev: remove DeviceType Gerd Hoffmann
2009-06-17 12:59 ` [Qemu-devel] [PATCH 04/10] qdev/pci: bus name Gerd Hoffmann
2009-06-17 12:59 ` [Qemu-devel] [PATCH 05/10] qdev: hook up i440fx Gerd Hoffmann
2009-06-17 12:59 ` [Qemu-devel] [PATCH 06/10] qdev: convert piix-ide, first step Gerd Hoffmann
2009-06-17 12:59 ` [Qemu-devel] [PATCH 07/10] qdev-ify: piix acpi Gerd Hoffmann
2009-06-17 12:59 ` [Qemu-devel] [PATCH 08/10] qdev-ify: uhci Gerd Hoffmann
2009-06-17 12:59 ` [Qemu-devel] [PATCH 09/10] qdev-ify: usb Gerd Hoffmann
2009-06-17 12:59 ` [Qemu-devel] [PATCH 10/10] qdev-ify: scsi Gerd Hoffmann
2009-06-18 14:39 ` [Qemu-devel] Re: [PATCH 0/10] qdev patches Gerd Hoffmann
2009-06-19 15:59 ` Gerd Hoffmann
2009-06-19 17:51 ` Paul Brook [this message]
2009-06-22 9:15 ` Gerd Hoffmann
2009-06-22 9:36 ` Avi Kivity
2009-06-22 9:57 ` Gerd Hoffmann
2009-06-22 11:25 ` Gerd Hoffmann
2009-06-22 11:29 ` Avi Kivity
2009-06-22 14:02 ` Gerd Hoffmann
2009-06-22 13:45 ` Gerd Hoffmann
2009-06-19 16:26 ` [Qemu-devel] " Paul Brook
2009-06-26 21:16 ` Markus Armbruster
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=200906191851.21563.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=kraxel@redhat.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).