qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: David Vrabel <david.vrabel@citrix.com>
To: Juergen Gross <jgross@suse.com>,
	qemu-devel@nongnu.org, xen-devel@lists.xensource.com
Cc: kraxel@redhat.com, stefano.stabellini@eu.citrix.com
Subject: Re: [Qemu-devel] [Xen-devel] [PATCH] xen: write information about supported backends
Date: Mon, 4 Apr 2016 10:18:15 +0100	[thread overview]
Message-ID: <57023157.6040807@citrix.com> (raw)
In-Reply-To: <1459347035-32740-1-git-send-email-jgross@suse.com>

On 30/03/16 15:10, Juergen Gross wrote:
> Add a Xenstore directory for each supported pv backend. This will allow
> Xen tools to decide which backend type to use in case there are
> multiple possibilities.
> 
> The information is added under
> /local/domain/<backend-domid>/device-model/<domid>/backends
> before the "running" state is written to Xenstore. Using a directory
> for each directory enables us to add parameters for specific backends
> in the future.

"Using a directory for each backend..."?
> 
> In order to reuse the Xenstore directory creation already present in
> hw/xen/xen_devconfig.c move the related functions to
> hw/xen/xen_backend.c where they fit better.

Why Xenstore and not QMP?

David

  parent reply	other threads:[~2016-04-04  9:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-30 14:10 [Qemu-devel] [PATCH] xen: write information about supported backends Juergen Gross
2016-04-01 14:56 ` Stefano Stabellini
2016-04-04  4:33   ` Juergen Gross
2016-04-06 17:12     ` Stefano Stabellini
2016-04-04  9:18 ` David Vrabel [this message]
2016-04-04  9:30   ` [Qemu-devel] [Xen-devel] " Juergen Gross

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=57023157.6040807@citrix.com \
    --to=david.vrabel@citrix.com \
    --cc=jgross@suse.com \
    --cc=kraxel@redhat.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).