From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Ian Campbell <Ian.Campbell@citrix.com>, david.vrabel@citrix.com
Cc: Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
xen-devel@lists.xensource.com, linux-kernel@vger.kernel.org
Subject: Re: [Xen-devel] [PATCH] allow xenfb initialization for hvm guests
Date: Wed, 18 Dec 2013 10:14:22 -0500 [thread overview]
Message-ID: <20131218151422.GF4934@phenom.dumpdata.com> (raw)
In-Reply-To: <1387367482.27441.123.camel@kazak.uk.xensource.com>
On Wed, Dec 18, 2013 at 11:51:22AM +0000, Ian Campbell wrote:
> On Tue, 2013-12-17 at 17:53 +0000, Stefano Stabellini wrote:
> > There is no reasons why an HVM guest shouldn't be allowed to use xenfb.
> > As a matter of fact ARM guests, HVM from Linux POV, can use xenfb.
> > Given that no Xen toolstacks configure a xenfb backend for x86 HVM
> > guests, they are not affected.
>
> and if a toolstack did I think it would be reasonable to expect the
> kernel to at least try and drive it!
>
> > Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
>
> Acked-by: Ian Campbell <ian.campbell@citrix.com>
I think David Vrabel is going to Nack it unless there is a test-case.
I am saying that because in his previous statement for Wei's multi-page
patches was that if there are no users (or at least no test-cases) then
it should not be part of the kernel.
next prev parent reply other threads:[~2013-12-18 15:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-17 17:53 Stefano Stabellini
2013-12-18 11:51 ` [Xen-devel] " Ian Campbell
2013-12-18 15:14 ` Konrad Rzeszutek Wilk [this message]
2013-12-18 15:18 ` Stefano Stabellini
2013-12-18 15:27 ` Konrad Rzeszutek Wilk
2013-12-18 17:32 ` Stefano Stabellini
2013-12-18 15:31 ` Andrew Cooper
2013-12-31 14:50 ` Konrad Rzeszutek Wilk
2014-01-02 12:52 ` David Vrabel
2014-01-03 18:38 ` 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=20131218151422.GF4934@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=Ian.Campbell@citrix.com \
--cc=david.vrabel@citrix.com \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome