All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Ian Campbell <Ian.Campbell@citrix.com>, <david.vrabel@citrix.com>,
	<xen-devel@lists.xensource.com>, <linux-kernel@vger.kernel.org>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [Xen-devel] [PATCH] allow xenfb initialization for hvm guests
Date: Wed, 18 Dec 2013 15:31:32 +0000	[thread overview]
Message-ID: <52B1BFD4.7090702@citrix.com> (raw)
In-Reply-To: <20131218151422.GF4934@phenom.dumpdata.com>

On 18/12/13 15:14, Konrad Rzeszutek Wilk wrote:
> 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.

Without trying to presume too much, I really don't think he would.

This patch is taking an existing thing and permitting it to work in more
cases (which is a good change IMO).

The multi-page rings was completely brand new functionality with no
consumers at all, so no ability to verify the implementation.  It is a
completely different context.

~Andrew

WARNING: multiple messages have this Message-ID (diff)
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Ian Campbell <Ian.Campbell@citrix.com>,
	david.vrabel@citrix.com, xen-devel@lists.xensource.com,
	linux-kernel@vger.kernel.org,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [Xen-devel] [PATCH] allow xenfb initialization for hvm guests
Date: Wed, 18 Dec 2013 15:31:32 +0000	[thread overview]
Message-ID: <52B1BFD4.7090702@citrix.com> (raw)
In-Reply-To: <20131218151422.GF4934@phenom.dumpdata.com>

On 18/12/13 15:14, Konrad Rzeszutek Wilk wrote:
> 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.

Without trying to presume too much, I really don't think he would.

This patch is taking an existing thing and permitting it to work in more
cases (which is a good change IMO).

The multi-page rings was completely brand new functionality with no
consumers at all, so no ability to verify the implementation.  It is a
completely different context.

~Andrew

  parent reply	other threads:[~2013-12-18 15:31 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-17 17:53 [PATCH] allow xenfb initialization for hvm guests Stefano Stabellini
2013-12-17 17:53 ` Stefano Stabellini
2013-12-18 11:51 ` [Xen-devel] " Ian Campbell
2013-12-18 11:51   ` Ian Campbell
2013-12-18 15:14   ` Konrad Rzeszutek Wilk
2013-12-18 15:18     ` Stefano Stabellini
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 17:32           ` Stefano Stabellini
2013-12-18 15:31     ` Andrew Cooper [this message]
2013-12-18 15:31       ` Andrew Cooper
2013-12-31 14:50 ` Konrad Rzeszutek Wilk
2014-01-02 12:52   ` David Vrabel
2014-01-02 12:52     ` David Vrabel
2014-01-03 18:38   ` Stefano Stabellini
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=52B1BFD4.7090702@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=david.vrabel@citrix.com \
    --cc=konrad.wilk@oracle.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 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.