From: Paul Brook <paul@codesourcery.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH 0/4][RFC] Add module infrastructure to QEMU
Date: Mon, 11 May 2009 17:16:35 +0100 [thread overview]
Message-ID: <200905111716.35553.paul@codesourcery.com> (raw)
In-Reply-To: <4A084CD2.7070108@us.ibm.com>
On Monday 11 May 2009, Anthony Liguori wrote:
> Paul Brook wrote:
> > On Monday 11 May 2009, Anthony Liguori wrote:
> >> This is the current state of a patch set to introduce a module
> >> infrastructure to QEMU.
> >
> > I don't think numeric priorities are a good idea. If we have dependencies
> > then we should be dealing with them properly, not hacking round the
> > problem.
>
> The numeric priorities are an implementation detail. No one should ever
> consume module_init() directly and I should add appropriately scary
> comments to that affect.
Having looked a bit deeper, you're not actually implementing priorities.
You're implementing different categories of init function. So this should be
an enum, and be renames to something less confusing.
> We do have dependencies. I'd like virtio to be a module, and I'd like
> virtio-net, virtio-blk, etc. to be modules. This gets exposed as
> virtio.c being a bus_init() and virtio-*.c being virtio_init(). We use
> the integer priorities in module.h to express this.
I'm not convinced virtio is as much of a separate entity as you think it is.
It's certainly not a bus. It's an implementation detail that happens to be
shared by several devices.
Paul
next prev parent reply other threads:[~2009-05-11 16:16 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-11 14:26 [Qemu-devel] [PATCH 0/4][RFC] Add module infrastructure to QEMU Anthony Liguori
2009-05-11 14:26 ` [Qemu-devel] [PATCH 1/4] " Anthony Liguori
2009-05-11 21:37 ` Jean-Christophe PLAGNIOL-VILLARD
2009-05-11 21:53 ` Anthony Liguori
2009-05-11 21:53 ` Jean-Christophe PLAGNIOL-VILLARD
2009-05-11 22:02 ` Anthony Liguori
2009-05-12 9:38 ` Gerd Hoffmann
2009-05-12 10:15 ` Paul Brook
2009-05-12 13:10 ` Anthony Liguori
[not found] ` <9EE414CC7AEE4488A45A263DE5B82EFE@jupiter>
2009-05-12 13:19 ` Anthony Liguori
2009-05-11 14:26 ` [Qemu-devel] [PATCH 2/4] Convert block infrastructure to use new module init functionality Anthony Liguori
2009-05-11 14:26 ` [Qemu-devel] [PATCH 3/4] Move block drivers into their own directory Anthony Liguori
2009-05-11 14:26 ` [Qemu-devel] [PATCH 4/4] Introduce global .config to selectively enable compile features Anthony Liguori
2009-05-11 15:22 ` Avi Kivity
2009-05-11 18:37 ` Anthony Liguori
2009-05-11 18:41 ` Avi Kivity
2009-05-11 14:48 ` [Qemu-devel] Re: [PATCH 0/4][RFC] Add module infrastructure to QEMU Paul Brook
2009-05-11 15:19 ` Avi Kivity
2009-05-11 16:10 ` [Qemu-devel] Re: [PATCH 0/4][RFC] Add module infrastructure toQEMU Anthony Liguori
2009-05-11 16:45 ` Avi Kivity
2009-05-11 16:05 ` [Qemu-devel] Re: [PATCH 0/4][RFC] Add module infrastructure to QEMU Anthony Liguori
2009-05-11 16:16 ` Paul Brook [this message]
2009-05-11 16:20 ` Anthony Liguori
2009-05-11 16:43 ` Paul Brook
[not found] ` <AEED36F4EA194EC2B57D5E4DB7D64896@jupiter>
2009-05-12 13:18 ` [Qemu-devel] " Anthony Liguori
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=200905111716.35553.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=aliguori@us.ibm.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).