All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony PERARD <anthony.perard@citrix.com>
To: Juergen Gross <jgross@suse.com>
Cc: qemu-devel@nongnu.org, xen-devel@lists.xensource.com,
	kraxel@redhat.com, sstabellini@kernel.org
Subject: Re: [Qemu-devel] [PATCH] xen: use a common function for pv and hvm guest backend register calls
Date: Tue, 2 Aug 2016 18:43:03 +0100	[thread overview]
Message-ID: <20160802174303.GV1835@perard.uk.xensource.com> (raw)
In-Reply-To: <1470119552-16170-1-git-send-email-jgross@suse.com>

On Tue, Aug 02, 2016 at 08:32:32AM +0200, Juergen Gross wrote:
> Instead of calling xen_be_register() for each supported backend type
> for hvm and pv guests in their machine init functions use a common
> function in order not to have to add new backends twice.
> 
> This at once fixes the error that hvm domains couldn't use the qusb
> backend.
> 
> Signed-off-by: Juergen Gross <jgross@suse.com>

Acked-by: Anthony PERARD <anthony.perard@citrix.com>

> ---
> Is it on purpose the qnic and vfb backends are not registered for HVM?

I guess it has not been usefull. Stefano may have a better answer.

-- 
Anthony PERARD

WARNING: multiple messages have this Message-ID (diff)
From: Anthony PERARD <anthony.perard@citrix.com>
To: Juergen Gross <jgross@suse.com>
Cc: xen-devel@lists.xensource.com, sstabellini@kernel.org,
	qemu-devel@nongnu.org, kraxel@redhat.com
Subject: Re: [PATCH] xen: use a common function for pv and hvm guest backend register calls
Date: Tue, 2 Aug 2016 18:43:03 +0100	[thread overview]
Message-ID: <20160802174303.GV1835@perard.uk.xensource.com> (raw)
In-Reply-To: <1470119552-16170-1-git-send-email-jgross@suse.com>

On Tue, Aug 02, 2016 at 08:32:32AM +0200, Juergen Gross wrote:
> Instead of calling xen_be_register() for each supported backend type
> for hvm and pv guests in their machine init functions use a common
> function in order not to have to add new backends twice.
> 
> This at once fixes the error that hvm domains couldn't use the qusb
> backend.
> 
> Signed-off-by: Juergen Gross <jgross@suse.com>

Acked-by: Anthony PERARD <anthony.perard@citrix.com>

> ---
> Is it on purpose the qnic and vfb backends are not registered for HVM?

I guess it has not been usefull. Stefano may have a better answer.

-- 
Anthony PERARD

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

  parent reply	other threads:[~2016-08-02 17:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-02  6:32 [Qemu-devel] [PATCH] xen: use a common function for pv and hvm guest backend register calls Juergen Gross
2016-08-02  6:32 ` Juergen Gross
2016-08-02 11:40 ` [Qemu-devel] " Gerd Hoffmann
2016-08-02 11:40   ` Gerd Hoffmann
2016-08-02 18:32   ` [Qemu-devel] " Stefano Stabellini
2016-08-02 18:32     ` Stefano Stabellini
2016-08-02 17:43 ` Anthony PERARD [this message]
2016-08-02 17:43   ` Anthony PERARD
2016-08-02 18:27 ` [Qemu-devel] " Stefano Stabellini
2016-08-02 18:27   ` Stefano Stabellini
2016-08-03  3:56   ` [Qemu-devel] " Juergen Gross
2016-08-03  3:56     ` Juergen Gross
2016-08-03 17:50     ` [Qemu-devel] " Stefano Stabellini
2016-08-03 17:50       ` Stefano Stabellini

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=20160802174303.GV1835@perard.uk.xensource.com \
    --to=anthony.perard@citrix.com \
    --cc=jgross@suse.com \
    --cc=kraxel@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=sstabellini@kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.