qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Wei Liu <wei.liu2@citrix.com>
To: xen-devel@lists.xen.org, qemu-devel@nongnu.org
Cc: anthony.perard@citrix.com, peter.maydell@linaro.org,
	Wei Liu <wei.liu2@citrix.com>,
	stefano.stabellini@eu.citrix.com
Subject: [Qemu-devel] [PATCH RFC 0/5] Xen: introduce Xen PV target
Date: Thu, 23 Jan 2014 22:16:01 +0000	[thread overview]
Message-ID: <1390515366-32236-1-git-send-email-wei.liu2@citrix.com> (raw)

As promised I hacked a prototype based on Paolo's disable TCG series.
However I coded some stubs for TCG anyway. So this series in principle
should work with / without Paolo's series.

The first 3 patches refactor some code to disentangle Xen PV and HVM
guest. The 4th patch has the real meat. It introduces Xen PV target,
which contains basically a dummy CPU, then hooks up this Xen PV CPU to
QEMU internal structures.

The last patch introduces xenpv-softmmu, which contains *no* emulation
code. I know that in previous discussion people said that every device
emulation should be included if the target architecture is called null.
But since this target CPU is now called xenpv I don't feel obliged to
include any device emulation in this prototype anymore. :-)

Please note that the existing Xen QEMU build is not affected at all. You
can still use "--disable-tcg --enable-xen --target-list=i386-softmmu"
(or x86_64-softmmu") to build qemu-system-{i386,x86_64} and use it for
both HVM and PV guest. This series adds another option to build QEMU with
"--disable-tcg --enable-xen --target-list=xenpv-softmmu" and get a QEMU
binary tailored for Xen PV guest. The effect is that we reduce the
binary size from 14MB to 7.3MB.

What do you think of this idea? I'm all ears.

Wei.

Wei Liu (5):
  xen: move Xen PV machine files to hw/xenpv
  xen: factor out common functions
  exec: guard Xen HVM hooks with CONFIG_XEN_I386
  xen: implement Xen PV target
  xen: introduce xenpv-softmmu.mak

 Makefile.target                      |    3 +-
 arch_init.c                          |    2 +
 configure                            |   12 ++-
 cpu-exec.c                           |    2 +
 default-configs/i386-softmmu.mak     |    1 -
 default-configs/x86_64-softmmu.mak   |    1 -
 default-configs/xenpv-softmmu.mak    |    2 +
 exec.c                               |   16 ++++
 hw/i386/Makefile.objs                |    2 +-
 hw/xenpv/Makefile.objs               |    2 +
 hw/{i386 => xenpv}/xen_domainbuild.c |    0
 hw/{i386 => xenpv}/xen_domainbuild.h |    0
 hw/{i386 => xenpv}/xen_machine_pv.c  |    0
 include/exec/memory-internal.h       |    2 +
 include/sysemu/arch_init.h           |    1 +
 target-xenpv/Makefile.objs           |    1 +
 target-xenpv/cpu-qom.h               |   64 ++++++++++++++++
 target-xenpv/cpu.h                   |   66 ++++++++++++++++
 target-xenpv/helper.c                |   32 ++++++++
 target-xenpv/translate.c             |   27 +++++++
 xen-common.c                         |  137 ++++++++++++++++++++++++++++++++++
 xen-all.c => xen-hvm.c               |  112 +--------------------------
 xen-stub.c                           |    4 -
 23 files changed, 368 insertions(+), 121 deletions(-)
 create mode 100644 default-configs/xenpv-softmmu.mak
 create mode 100644 hw/xenpv/Makefile.objs
 rename hw/{i386 => xenpv}/xen_domainbuild.c (100%)
 rename hw/{i386 => xenpv}/xen_domainbuild.h (100%)
 rename hw/{i386 => xenpv}/xen_machine_pv.c (100%)
 create mode 100644 target-xenpv/Makefile.objs
 create mode 100644 target-xenpv/cpu-qom.h
 create mode 100644 target-xenpv/cpu.h
 create mode 100644 target-xenpv/helper.c
 create mode 100644 target-xenpv/helper.h
 create mode 100644 target-xenpv/translate.c
 create mode 100644 xen-common.c
 rename xen-all.c => xen-hvm.c (92%)

-- 
1.7.10.4

             reply	other threads:[~2014-01-23 22:16 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-23 22:16 Wei Liu [this message]
2014-01-23 22:16 ` [Qemu-devel] [PATCH RFC 1/5] xen: move Xen PV machine files to hw/xenpv Wei Liu
2014-01-23 22:16 ` [Qemu-devel] [PATCH RFC 2/5] xen: factor out common functions Wei Liu
2014-01-23 22:16 ` [Qemu-devel] [PATCH RFC 3/5] exec: guard Xen HVM hooks with CONFIG_XEN_I386 Wei Liu
2014-01-24  7:35   ` Paolo Bonzini
2014-01-23 22:16 ` [Qemu-devel] [PATCH RFC 4/5] xen: implement Xen PV target Wei Liu
2014-01-23 22:16 ` [Qemu-devel] [PATCH RFC 5/5] xen: introduce xenpv-softmmu.mak Wei Liu
2014-01-24  7:38   ` Paolo Bonzini
2014-01-24 17:00     ` Wei Liu
2014-01-23 22:30 ` [Qemu-devel] [PATCH RFC 0/5] Xen: introduce Xen PV target Peter Maydell
2014-01-24 14:23   ` Wei Liu
2014-01-24 14:38     ` Paolo Bonzini
2014-01-24 14:50       ` Wei Liu
2014-01-24 14:30   ` Paolo Bonzini
2014-01-24 14:35     ` Peter Maydell
2014-01-24 14:42       ` Paolo Bonzini
2014-01-24 14:56         ` Stefano Stabellini
2014-01-24 15:22           ` [Qemu-devel] [Xen-devel] " Ian Campbell
2014-01-24  7:36 ` [Qemu-devel] " 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=1390515366-32236-1-git-send-email-wei.liu2@citrix.com \
    --to=wei.liu2@citrix.com \
    --cc=anthony.perard@citrix.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xen.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).