xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Jim Fehlig <jfehlig@suse.com>
To: libvir-list@redhat.com
Cc: xen-devel@lists.xen.org
Subject: [PATCH 0/5] libxl: user-specified domain config improvements
Date: Fri, 19 Sep 2014 13:23:09 -0600	[thread overview]
Message-ID: <1411154594-14871-1-git-send-email-jfehlig@suse.com> (raw)

This is essentially a V2 of Stefan's patch to add support
for user-specified video device in the libxl driver.

https://www.redhat.com/archives/libvir-list/2014-September/msg01157.html

It goes a bit further and adds support for user-specfied <emulator>,
which was trivial to add after introducing libxlDomainGetEmulatorType
in patch 3.  To ease review, the series has been split up as follows:

- Missed keymap config from commit 4dfc34c3 split out to patch 1
- Patch 2 added to defer setting default vram value to the Xen drivers
- Patch 3 added to detect old qemu-dm vs qemu with xen support
- Patch 4 is a slightly reworked version of Stefan's patch
- Patch 5 added to support user-specified <emulator>

Jim Fehlig (4):
  libxl: Copy user-specified keymap to libxl build info struct
  Xen: Defer setting default vram value to Xen drivers
  libxl: Add function to determine device model type
  libxl: Support user-specified <emulator>

Stefan Bader (1):
  libxl: Implement basic video device selection

 src/conf/domain_conf.c   |   4 ++
 src/libxl/libxl_conf.c   | 124 +++++++++++++++++++++++++++++++++++++++++++++++
 src/libxl/libxl_conf.h   |   3 ++
 src/libxl/libxl_domain.c |  22 +++++++++
 src/xen/xen_driver.c     |  19 ++++++++
 5 files changed, 172 insertions(+)

-- 
1.8.4.5

             reply	other threads:[~2014-09-19 19:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-19 19:23 Jim Fehlig [this message]
2014-09-19 19:23 ` [PATCH 1/5] libxl: Copy user-specified keymap to libxl build info struct Jim Fehlig
2014-09-19 19:23 ` [PATCH 2/5] Xen: Defer setting default vram value to Xen drivers Jim Fehlig
2014-10-06  8:04   ` [libvirt] " Michal Privoznik
2014-09-19 19:23 ` [PATCH 3/5] libxl: Add function to determine device model type Jim Fehlig
2014-09-19 19:23 ` [PATCH 4/5] libxl: Implement basic video device selection Jim Fehlig
2014-10-14  8:47   ` [libvirt] " John Ferlan
     [not found]   ` <543CE32F.8070407@redhat.com>
2014-10-16 19:16     ` Jim Fehlig
2014-09-19 19:23 ` [PATCH 5/5] libxl: Support user-specified <emulator> Jim Fehlig
2014-10-06  8:04   ` [libvirt] " Michal Privoznik
2014-10-06  8:03 ` [libvirt] [PATCH 0/5] libxl: user-specified domain config improvements Michal Privoznik
     [not found] ` <1411154594-14871-4-git-send-email-jfehlig@suse.com>
2014-10-06  8:04   ` [libvirt] [PATCH 3/5] libxl: Add function to determine device model type Michal Privoznik
     [not found]   ` <54324CF3.8050507@redhat.com>
2014-10-10 21:22     ` Jim Fehlig
     [not found] ` <54324CEE.5000505@redhat.com>
2014-10-10 21:23   ` [libvirt] [PATCH 0/5] libxl: user-specified domain config improvements Jim Fehlig

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=1411154594-14871-1-git-send-email-jfehlig@suse.com \
    --to=jfehlig@suse.com \
    --cc=libvir-list@redhat.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).