xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Simon Waterman <watermansrdev@gmail.com>
To: xen-devel@lists.xen.org
Cc: ian.jackson@eu.citrix.com, wei.liu2@citrix.com
Subject: [PATCH RFC 0/3] libxl: upstream Qemu as PV backend for IOEMU stubdom
Date: Sun, 25 Jun 2017 23:15:28 +0100	[thread overview]
Message-ID: <1498428931-465-1-git-send-email-watermansrdev@gmail.com> (raw)

This patch adds support for choosing upstream QEMU as the PV QEMU
backend for an IOEMU stubdom instead of qemu-xen-traditional.
The motivation is to expose QEMU features only available in upstream
like VNC auth options.

It adds a new xl.cfg file parameter named device_model_pv_version taking
the same values as device_model_version.  I made the choice configurable
as upstream QEMU requires more RAM than qemu-xen-traditional.

This patch was prompted by guidance from Ian when my SASL patch to
qemu-xen-trad was deemed too complicated.

 libxl/libxl_dm.c      |    6 ++++--
 libxl/libxl_types.idl |    1 +
 xl/xl_parse.c         |   19 +++++++++++++++++++
 3 files changed, 24 insertions(+), 2 deletions(-)


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

             reply	other threads:[~2017-06-25 22:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-25 22:15 Simon Waterman [this message]
2017-06-25 22:15 ` [PATCH RFC 1/3] libxl: upstream Qemu as PV backend for IOEMU stubdom Simon Waterman
2017-06-25 22:15 ` [PATCH RFC 2/3] " Simon Waterman
2017-06-25 22:15 ` [PATCH RFC 3/3] " Simon Waterman
2017-06-28 17:36 ` [PATCH RFC 0/3] " Wei 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=1498428931-465-1-git-send-email-watermansrdev@gmail.com \
    --to=watermansrdev@gmail.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=wei.liu2@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).