From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Breaking up vl.h
Date: Sat, 17 Nov 2007 17:13:48 +0000 [thread overview]
Message-ID: <200711171713.49528.paul@codesourcery.com> (raw)
I just applied a patch that breaks up and removes vl.h
My strategy (as discussed previously) is to split the contents along
functional lines, and hardware split along bus/machine boundaries..
In order to avoid lots of little header files it makes fairly extensive use of
opaque structure pointers. This allows e.g. network and display controllers
to be prototyped in the same header without requiring all users to include
net.h and console.h.
It's not perfect, but I'm reasonably happy with how it ended up. There's some
scope for splitting things up further, but I tended to err on the size of a
few big includes.
Paul
reply other threads:[~2007-11-17 17:14 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=200711171713.49528.paul@codesourcery.com \
--to=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).