From mboxrd@z Thu Jan 1 00:00:00 1970 From: Juergen Gross Subject: Re: [Xen-devel] [PATCH] xen: write information about supported backends Date: Mon, 4 Apr 2016 11:30:54 +0200 Message-ID: <5702344E.6030309@suse.com> References: <1459347035-32740-1-git-send-email-jgross@suse.com> <57023157.6040807@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <57023157.6040807@citrix.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org Sender: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org To: David Vrabel , qemu-devel@nongnu.org, xen-devel@lists.xensource.com Cc: kraxel@redhat.com, stefano.stabellini@eu.citrix.com List-Id: xen-devel@lists.xenproject.org On 04/04/16 11:18, David Vrabel wrote: > 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//device-model//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..."? Yes. As I've written: this enables us to enhance the interface later without the need to modify it first. >> 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? We need to communicate with qemu only once instead of each time a device is added to the domain. Doing the communication via Xenstore is much simpler. Juergen