From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH 0/3] more vl.c/monitor.c splits
Date: Fri, 19 Mar 2010 11:35:06 +0100 [thread overview]
Message-ID: <1268994909-7107-1-git-send-email-pbonzini@redhat.com> (raw)
I've had these for a while, but as they conflicted with the timer patch
I waited before sending them.
Paolo Bonzini (3):
move socket_init to qemu-sockets.c
move two variable declarations out of vl.c
move balloon handling to balloon.c
Makefile.target | 2 +-
balloon.c | 145 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
balloon.h | 6 ++
hw/i8259.c | 1 +
hw/isa-bus.c | 1 +
monitor.c | 85 --------------------------------
qemu-sockets.c | 24 +++++++++
qemu_socket.h | 1 +
vl.c | 64 ------------------------
9 files changed, 179 insertions(+), 150 deletions(-)
create mode 100644 balloon.c
next reply other threads:[~2010-03-19 10:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-19 10:35 Paolo Bonzini [this message]
2010-03-19 10:35 ` [Qemu-devel] [PATCH 1/3] move socket_init to qemu-sockets.c Paolo Bonzini
2010-03-19 10:35 ` [Qemu-devel] [PATCH 2/3] move two variable declarations out of vl.c Paolo Bonzini
2010-03-19 10:35 ` [Qemu-devel] [PATCH 3/3] move balloon handling to balloon.c Paolo Bonzini
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=1268994909-7107-1-git-send-email-pbonzini@redhat.com \
--to=pbonzini@redhat.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).