From: Blue Swirl <blauwirbel@gmail.com>
To: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] [PATCH 0/3] Compile some files only once
Date: Thu, 15 Apr 2010 22:08:05 +0300 [thread overview]
Message-ID: <n2pf43fc5581004151208oec3ce8f9j9a12dd84f9260093@mail.gmail.com> (raw)
I think Paolo's approach can work even with vl.c including kvm.h,
provided that kvm.h remains such that it can be used safely.
The situation is a bit fragile though. Some kind of poisoning,
splitting kvm.h into two files, or other means should be used to make
kvm.h more robust.
Blue Swirl (2):
Compile vl.c once
Compile event_notifier only once
Paolo Bonzini (1):
provide a stub version of kvm-all.c if !CONFIG_KVM
Makefile.objs | 4 +-
Makefile.target | 5 +-
kvm-all.c | 6 ++-
kvm-stub.c | 135 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
kvm.h | 13 +----
vl.c | 16 +++----
6 files changed, 154 insertions(+), 25 deletions(-)
create mode 100644 kvm-stub.c
reply other threads:[~2010-04-15 19:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=n2pf43fc5581004151208oec3ce8f9j9a12dd84f9260093@mail.gmail.com \
--to=blauwirbel@gmail.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).