qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Chunyan Liu <cyliu@suse.com>
To: xen-devel@lists.xensource.com, qemu-devel@nongnu.org
Cc: Chunyan Liu <cyliu@suse.com>,
	Ian.Jackson@eu.citrix.com, Ian.Campbell@citrix.com,
	stefano.stabellini@eu.citrix.com
Subject: [Qemu-devel] [RFC PATCH V5 0/3] Support xen HVM direct kernel boot
Date: Mon,  7 Jul 2014 14:34:32 +0800	[thread overview]
Message-ID: <1404714875-24362-1-git-send-email-cyliu@suse.com> (raw)

Updated current patch series for working with qemu-xen and default
BIOS (seabios), to make it in good shape. Stubdom support will be
continued.
  
xen side patches: 
    * pass kernel/initrd/append parameters to qemu-dm
    * add 'cmdline' in xl.cfg
qemu side patch: reuse load_linux() for xen hvm direct kernel boot.
    Different from pc_memory_init which does lots of ram alloc work
    and rom/bios loading work, for xen, we only need to init a basic
    fw_cfg device used by load_linux() to store ADDRs and
    linuxboot.bin/multiboot.bin to retrive ADDRs, then load_linux(),
    after that, do real add option rom work to add
    linuxboot.bin/multiboot.bin to system option rom. Other things
    would be done by seabios smoothly.

Changes:
  xen side patch:
    - add 'cmdline' in xl.cfg (as a separate patch)
    - update u.pv.kernel compable work: fill in b_info.kernel with
      old u.pv.kernel in libxl__domain_build_info_setdefault, handle
      b_info.kernel only later.
    - update libxl.h to include LIBXL_HAVE_BUILDINFO_KERNEL only
      rather than three
  qemu side patch:
    - no change to v4.

v4 is here:
http://lists.gnu.org/archive/html/qemu-devel/2014-07/msg00026.html

v3 is here:
https://lists.nongnu.org/archive/html/qemu-devel/2014-06/msg04903.html

v2 is here:
http://thread.gmane.org/gmane.comp.emulators.qemu/277514

v1 is here:
http://lists.gnu.org/archive/html/qemu-devel/2014-05/msg06233.html

Chunyan Liu (3):
  xen: pass kernel initrd to qemu
  xl.cfg: add 'cmdline' in config file
  qemu: support xen HVM direct kernel boot

-- 
1.8.4.5

             reply	other threads:[~2014-07-07  6:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-07  6:34 Chunyan Liu [this message]
2014-07-07  6:34 ` [Qemu-devel] [RFC PATCH V5 1/3] xen: pass kernel initrd to qemu Chunyan Liu
2014-07-10 14:48   ` Ian Campbell
2014-11-27 18:14   ` [Qemu-devel] [for 4.5] missing chunk in 11dffa2359e8a2629490c14c029c7c7c777b3e47 Stefano Stabellini
2014-11-28  6:03     ` Chun Yan Liu
2014-07-07  6:34 ` [Qemu-devel] [RFC PATCH V5 2/3] xl.cfg: add 'cmdline' in config file Chunyan Liu
2014-07-10 14:49   ` Ian Campbell
2014-07-07  6:34 ` [Qemu-devel] [RFC PATCH V5 3/3] qemu: support xen hvm direct kernel boot Chunyan Liu
2014-07-10 15:12 ` [Qemu-devel] [RFC PATCH V5 0/3] Support xen HVM " Ian Campbell
2014-07-10 15:14   ` Stefano Stabellini
2014-08-04 17:26     ` Stefano Stabellini
2014-08-26 21:02       ` Ian Campbell
2014-08-27  3:26         ` Chun Yan Liu

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=1404714875-24362-1-git-send-email-cyliu@suse.com \
    --to=cyliu@suse.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xensource.com \
    /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).