From: Thiemo Seufer <ths@networkno.de>
To: Paul Brook <paul@codesourcery.com>
Cc: Blue Swirl <blauwirbel@gmail.com>, "J. Mayer" <l_indien@magic.fr>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] How to split vl.h
Date: Sun, 4 Nov 2007 23:38:34 +0000 [thread overview]
Message-ID: <20071104233834.GH9363@networkno.de> (raw)
In-Reply-To: <200711042130.20231.paul@codesourcery.com>
Paul Brook wrote:
> > > I not sure a single hw/hw.h file will give any benefit because there's a
> > > fair amount of interfacing between the target devices emulation and the
> > > host side interaction code. i.e. there's not much that's only used inside
> > > hw/. hw/ is about as big as most of the rest of qemu put together, so
> > > splitting that is probably going to get the biggest wins.
> >
> > hw library contains a lot of code but is not all is compiled for all
> > targets.
>
> *shrug*. When I'm developing I generally only build the target I'm interested
> in anyway. If I'm doing a verification build before committing I'll build
> from scratch anyway. I've been bitten by faulty dependency checking
> (automatic or otherwise) often enough that I don't trust it for anything
> important.
Dependency checking appears to work well now.
Thiemo
next prev parent reply other threads:[~2007-11-04 23:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-31 18:12 [Qemu-devel] How to split vl.h Blue Swirl
2007-10-31 19:35 ` Jocelyn Mayer
2007-10-31 23:06 ` Thiemo Seufer
2007-11-01 11:16 ` Fabrice Bellard
2007-11-01 13:32 ` Stefan Weil
2007-11-01 14:11 ` andrzej zaborowski
2007-11-04 8:48 ` Blue Swirl
2007-11-04 12:17 ` Paul Brook
2007-11-04 17:23 ` J. Mayer
2007-11-04 17:54 ` Paul Brook
2007-11-04 19:41 ` J. Mayer
2007-11-04 21:30 ` Paul Brook
2007-11-04 23:38 ` Thiemo Seufer [this message]
2007-11-04 18:06 ` Thiemo Seufer
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=20071104233834.GH9363@networkno.de \
--to=ths@networkno.de \
--cc=blauwirbel@gmail.com \
--cc=l_indien@magic.fr \
--cc=paul@codesourcery.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).