From: Fam Zheng <famz@redhat.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] why we build only some optional modules as modules?
Date: Tue, 8 Apr 2014 09:02:39 +0800 [thread overview]
Message-ID: <20140408010239.GB2168@T430.redhat.com> (raw)
In-Reply-To: <5340F160.4050804@msgid.tls.msk.ru>
On Sun, 04/06 10:17, Michael Tokarev wrote:
> 06.04.2014 04:52, Fam Zheng wrote:
> > On Sat, 04/05 18:29, Michael Tokarev wrote:
> >> A quick (hopefully) question.
> >>
> >> Why build-as-modules only enabled for a few optional modules only,
> >> why not build as modules everything, to reduce common executable
> >> size? Or is it not a concern anymore at our disk sizes? :)
> >
> > The original demand was to reduce package dependencies of distribution QEMU,
> > hence not everything is (planned to be) modularized.
>
> Please note that current situation/implementation has one detail which
> prevents this usage: when any module is missing, qemu complains at
> startup about this. So at this stage, the original goal is not met. ;)
True but I don't know either, my original patch didn't complain about this. :)
>
> > But there is no blocking reason to turn other things to modules as well,
> > AFAICT.
>
> I think so, too, yes.
>
And it would be good if you have a reason to do it.
Fam
prev parent reply other threads:[~2014-04-08 1:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-05 14:29 [Qemu-devel] why we build only some optional modules as modules? Michael Tokarev
2014-04-06 0:52 ` Fam Zheng
2014-04-06 6:17 ` Michael Tokarev
2014-04-08 1:02 ` Fam Zheng [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=20140408010239.GB2168@T430.redhat.com \
--to=famz@redhat.com \
--cc=mjt@tls.msk.ru \
--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.