All of lore.kernel.org
 help / color / mirror / Atom feed
From: George Dunlap <george.dunlap@eu.citrix.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: xen-devel@lists.xensource.com, keir@xen.org,
	Tim Deegan <Tim.Deegan@citrix.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Lars Kurth <lars.kurth@xen.org>,
	DavidVrabel <david.vrabel@citrix.com>,
	Jan Beulich <JBeulich@suse.com>,
	Ian Campbell <Ian.Campbell@citrix.com>
Subject: Re: Xen Project policy on feature flags
Date: Mon, 29 Sep 2014 10:00:13 +0100	[thread overview]
Message-ID: <54291F9D.4030705@eu.citrix.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1409261540570.16742@kaball.uk.xensource.com>

On 09/26/2014 03:49 PM, Stefano Stabellini wrote:
>> Let me rephrase - will it boot in the same fashion (And with the same
>> bugs) as it did prior to this functionality being introduced?
> 3.15 -> dom0 on ARM broken (if netback is used)
> 3.17 -> dom0 on ARM is fixed, only if the kernel is compiled with CONFIG_ARM_LPAE
>
> Reverting the XENFEAT_grant_map_identity related changes would give you
> a system broken even with CONFIG_ARM_LPAE.
> Reverting Zoltan's changes to netback would give you a working system.

So the *only* reason to include this flag at this point is to allow 
people to run an unmodified 3.17 kernel with netback, is that right?  It 
seems like a really jerk move to encourage people to put 3.17 on their 
systems, and then deliberately break it on a subsequent release.

Particularly with ARM, where people are used to doing platform-specific 
things, it seems like encouraging people to either use pre-3.15 or to 
revert Zoltan's changes would be a better option.

  -George

  reply	other threads:[~2014-09-29  9:00 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-26 13:24 Xen Project policy on feature flags Stefano Stabellini
2014-09-26 13:39 ` Jan Beulich
2014-09-26 13:56   ` Andrew Cooper
2014-09-26 14:19   ` Ian Campbell
2014-09-26 14:29     ` Konrad Rzeszutek Wilk
2014-09-26 14:49       ` Stefano Stabellini
2014-09-29  9:00         ` George Dunlap [this message]
2014-09-29  9:31           ` Wei Liu
2014-09-29  9:36             ` George Dunlap
2014-09-29  9:54               ` Wei Liu
2014-09-29  9:54                 ` Stefano Stabellini
2014-09-29 10:05               ` David Vrabel
2014-09-29 11:32                 ` Ian Campbell
2014-09-29 14:55                   ` Konrad Rzeszutek Wilk
2014-09-29 15:00                     ` Ian Campbell
2014-09-30 11:04                       ` Stefano Stabellini
2014-09-26 14:46     ` Jan Beulich
2014-09-26 14:26 ` David Vrabel
2014-09-26 14:36   ` Konrad Rzeszutek Wilk
2014-09-26 14:54     ` Stefano Stabellini
2014-09-26 19:16       ` Konrad Rzeszutek Wilk
2014-09-26 14:52   ` Jan Beulich

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=54291F9D.4030705@eu.citrix.com \
    --to=george.dunlap@eu.citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=JBeulich@suse.com \
    --cc=Tim.Deegan@citrix.com \
    --cc=david.vrabel@citrix.com \
    --cc=keir@xen.org \
    --cc=konrad.wilk@oracle.com \
    --cc=lars.kurth@xen.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.