xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Stefano Stabellini <sstabellini@kernel.org>
To: Julien Grall <julien.grall@arm.com>
Cc: xen-devel@lists.xenproject.org,
	Dirk Behme <dirk.behme@de.bosch.com>,
	Stefano Stabellini <sstabellini@kernel.org>
Subject: Re: [PATCH v2] xen: arm: Update arm64 image header
Date: Wed, 22 Jun 2016 16:17:27 +0100 (BST)	[thread overview]
Message-ID: <alpine.DEB.2.10.1606221617180.2575@sstabellini-ThinkPad-X260> (raw)
In-Reply-To: <576AA6F9.5020008@arm.com>

On Wed, 22 Jun 2016, Julien Grall wrote:
> Hi Konrad,
> 
> On 22/06/16 15:29, Konrad Rzeszutek Wilk wrote:
> > > > Oh, indeed!
> > > > > 
> > > > > 
> > > > > My patch doesn't change anything regarding the fact that if the magics
> > > > > are
> > > > > not valid (due to quite old kernel version) the code does exit with an
> > > > > error.
> > > > 
> > > > /me nods
> > > > > 
> > > > > While the review of v1 of this patch, Julien asked for an error
> > > > > message to
> > > > > be added here. Fine.
> > > > > 
> > > > > But if there is the request to change the behavior regarding which
> > > > > kernels
> > > > > are supported I'd think that this is independent on this patch and
> > > > > should be
> > > > > done in an additional patch.
> > > > 
> > > > Right, and I think it is fine to skip that  - because as you say - it
> > > > already ignores older kernels.
> > > 
> > > This is not right. The current version of Xen is not ignoring older
> > > kernels.
> > > 
> > > The current check allows kernels with only MAGIC_V0 (any Linux older than
> > > 3.12) to be detected by Xen.
> > > 
> > > However, this is impacting only one version because support for Xen on
> > > ARM64
> > > was added in Linux 3.11.
> > 
> > And you ARM maintainers are OK ditching that support?
> 
> The number of board supported by Linux 3.11 on ARM64 is very limited: ARM
> models and X-gene.
> 
> For the latter it was an early support with only the serial and timer
> upstreamed (see [1]).
> 
> So personally I am fine with that. Any opinions?

I agree with that

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

      reply	other threads:[~2016-06-22 15:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-22  8:59 [PATCH v2] xen: arm: Update arm64 image header Dirk Behme
2016-06-22 13:30 ` Konrad Rzeszutek Wilk
2016-06-22 13:44   ` Julien Grall
2016-06-22 14:03     ` Dirk Behme
2016-06-22 13:44   ` Dirk Behme
2016-06-22 13:51     ` Konrad Rzeszutek Wilk
2016-06-22 13:57       ` Julien Grall
2016-06-22 14:29         ` Konrad Rzeszutek Wilk
2016-06-22 14:55           ` Julien Grall
2016-06-22 15:17             ` Stefano Stabellini [this message]

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=alpine.DEB.2.10.1606221617180.2575@sstabellini-ThinkPad-X260 \
    --to=sstabellini@kernel.org \
    --cc=dirk.behme@de.bosch.com \
    --cc=julien.grall@arm.com \
    --cc=xen-devel@lists.xenproject.org \
    /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;
as well as URLs for NNTP newsgroup(s).