All of lore.kernel.org
 help / color / mirror / Atom feed
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] arm64: ignore memory outside of the linear range
Date: Tue, 25 Aug 2015 11:02:54 +0100	[thread overview]
Message-ID: <20150825100254.GB21300@arm.com> (raw)
In-Reply-To: <CAKv+Gu-d77ab78WfT8r9YovrNXwFtpq4K9uKmSq5E1jOmRitYw@mail.gmail.com>

On Tue, Aug 25, 2015 at 10:45:01AM +0100, Ard Biesheuvel wrote:
> On 25 August 2015 at 00:34, Stuart Yoder <stuart.yoder@freescale.com> wrote:
> >> On Mon, Aug 24, 2015 at 02:58:26PM +0100, Stuart Yoder wrote:
> >> > Are we sending to stable as well?
> >>
> >> I've already pushed the patch out without a Cc stable (it's not a
> >> regression afaict), so if you want it backported then you'll need to send
> >> it to stable separately.
> >
> > Ok, was asking because of Catalin's previous comment:
> >
> >  > Even though it is not a regression, I think it is a bug fix and it's
> >  > worth cc'ing stable (though we could push it after 4.3-rc1).
> >
> 
> Indeed. Catalin also mentioned that you and he discussed a minimal fix
> with a cc to stable, only the fix itself was flawed. So let's not make
> this Stuart's problem, considering that this issue breaks all arm64
> systems with 32+ GB of RAM if they follow ARM's own recommendation
> regarding the physical layout of memory.
> 
> > Ard, are you going to send to stable?
> >
> 
> We'll have to wait until the merge window closes, of course, but yes,
> we should propose it.
> 
> @Will: what do you think? It would be nice to have you on record with
> an opinion rather than leaving it up to Stuart.

This isn't something that has *ever* worked with the arm64 kernel,
right? In which case, it's not a regression, it's more like adding
support for some systems that we've not supported before. Now, given the
nature of the patch, I'm not against stable, but by the time Stuart
pointed that out, I'd already pushed the patch and I don't want to
rebase our 4.3 queue at this stage.

The best bet is to send this to stable once it's in mainline (i.e. -rc1)
and I think it makes sense for Stuart to do that, since he is the one
most interested in having that happen.

Will

  parent reply	other threads:[~2015-08-25 10:02 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-18  9:34 [PATCH 0/2] arm64: ignore memory outside of the linear range Ard Biesheuvel
2015-08-18  9:34 ` [PATCH 1/2] of/fdt: make memblock maximum physical address arch configurable Ard Biesheuvel
2015-08-20  9:18   ` Catalin Marinas
2015-08-23 22:01   ` Rob Herring
2015-08-18  9:34 ` [PATCH 2/2] arm64: set MAX_MEMBLOCK_ADDR according to linear region size Ard Biesheuvel
2015-08-18 10:00   ` Will Deacon
2015-08-18 10:04     ` Ard Biesheuvel
2015-08-18 17:39       ` Catalin Marinas
2015-08-18 17:44         ` Ard Biesheuvel
2015-08-19  9:15           ` Catalin Marinas
2015-08-20  5:09         ` Ard Biesheuvel
2015-08-20  9:17           ` Catalin Marinas
2015-08-18 14:24     ` Catalin Marinas
2015-08-18 14:31       ` Ard Biesheuvel
2015-08-18 14:38         ` Ard Biesheuvel
2015-08-18 14:51       ` Russell King - ARM Linux
2015-08-18 16:16         ` Catalin Marinas
2015-08-20  9:19   ` Catalin Marinas
2015-08-20 11:54     ` Ard Biesheuvel
2015-08-20 12:50       ` Catalin Marinas
2015-08-18 14:18 ` [PATCH 0/2] arm64: ignore memory outside of the linear range Stuart Yoder
2015-08-24  8:00   ` Ard Biesheuvel
2015-08-24  9:22     ` Will Deacon
2015-08-24 13:58       ` Stuart Yoder
2015-08-24 14:08         ` Will Deacon
2015-08-24 22:34           ` Stuart Yoder
2015-08-25  9:45             ` Ard Biesheuvel
2015-08-25  9:54               ` Russell King - ARM Linux
2015-08-25 10:02               ` Will Deacon [this message]
2015-08-25 10:10                 ` Ard Biesheuvel

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=20150825100254.GB21300@arm.com \
    --to=will.deacon@arm.com \
    --cc=linux-arm-kernel@lists.infradead.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 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.