[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-devel] Re: [PATCH 0/4][RFC] Add module infrastructure to QEMU
From: |
Paul Brook |
Subject: |
[Qemu-devel] Re: [PATCH 0/4][RFC] Add module infrastructure to QEMU |
Date: |
Mon, 11 May 2009 15:48:47 +0100 |
User-agent: |
KMail/1.9.9 |
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.
Also, there's no reason to have destructors. The init function can register
these at runtime.
> 2) Switch to using dynamic shared libraries. This has the benefit of
> reducing the QEMU install size. This is attractive except for the fact
> that creating dynamic shared libraries across multiple host architectures
> is a pain.
In practice I'd expect the shared library overhead (both disk and RAM) to be
significantly larger than the saving form omitting a few devices. As you said
before, if we're not using something, why build it in the first place?
There's also the issue that shared libraries imply it's OK for third parties
to ship binary plugins.
Paul
[Qemu-devel] [PATCH 2/4] Convert block infrastructure to use new module init functionality, Anthony Liguori, 2009/05/11
[Qemu-devel] [PATCH 4/4] Introduce global .config to selectively enable compile features, Anthony Liguori, 2009/05/11
[Qemu-devel] [PATCH 3/4] Move block drivers into their own directory, Anthony Liguori, 2009/05/11
[Qemu-devel] Re: [PATCH 0/4][RFC] Add module infrastructure to QEMU,
Paul Brook <=
[Qemu-devel] Re: [PATCH 0/4][RFC] Add module infrastructure to QEMU, Anthony Liguori, 2009/05/11
Message not available