From: jeremy.linton@arm.com (Jeremy Linton)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: Disallow combination of ARCH_XGENE and 16K page size
Date: Thu, 28 Jan 2016 08:50:04 -0600 [thread overview]
Message-ID: <56AA2A9C.5080602@arm.com> (raw)
In-Reply-To: <20160128112033.GI17123@leverpostej>
On 01/28/2016 05:20 AM, Mark Rutland wrote:
> On Thu, Jan 28, 2016 at 11:08:20AM +0000, Will Deacon wrote:
>> On Thu, Jan 28, 2016 at 10:34:41AM +0000, Catalin Marinas wrote:
>> I thought there was also a suggestion that we could fail gracefully in
>> the EFI stub if we detected an unsupported page size?
>
> Yup. There are other things we could/should test, too.
>
> I believe Jeremy had a patch, but due to churn in that area it didn't
> get picked up.
I will clean-up and re-post that patch in the future too. It was fairly
trivial so if someone feels the need for immediately...
https://lkml.org/lkml/2015/10/14/948
IMHO, The main sticking point initially was that the correct place for
the check was a moving target. That problem has been fixed, so it should
be easy to move it.
WARNING: multiple messages have this Message-ID (diff)
From: Jeremy Linton <jeremy.linton@arm.com>
To: Mark Rutland <mark.rutland@arm.com>,
Will Deacon <will.deacon@arm.com>,
ard.biesheuvel@linaro.org
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Feng Kan <fkan@apm.com>,
dann frazier <dann.frazier@canonical.com>,
Duc Dang <dhdang@apm.com>,
linux-kernel@vger.kernel.org, Loc Ho <lho@apm.com>,
Kumar Sankaran <ksankaran@apm.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64: Disallow combination of ARCH_XGENE and 16K page size
Date: Thu, 28 Jan 2016 08:50:04 -0600 [thread overview]
Message-ID: <56AA2A9C.5080602@arm.com> (raw)
In-Reply-To: <20160128112033.GI17123@leverpostej>
On 01/28/2016 05:20 AM, Mark Rutland wrote:
> On Thu, Jan 28, 2016 at 11:08:20AM +0000, Will Deacon wrote:
>> On Thu, Jan 28, 2016 at 10:34:41AM +0000, Catalin Marinas wrote:
>> I thought there was also a suggestion that we could fail gracefully in
>> the EFI stub if we detected an unsupported page size?
>
> Yup. There are other things we could/should test, too.
>
> I believe Jeremy had a patch, but due to churn in that area it didn't
> get picked up.
I will clean-up and re-post that patch in the future too. It was fairly
trivial so if someone feels the need for immediately...
https://lkml.org/lkml/2015/10/14/948
IMHO, The main sticking point initially was that the correct place for
the check was a moving target. That problem has been fixed, so it should
be easy to move it.
next prev parent reply other threads:[~2016-01-28 14:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-27 23:10 [PATCH] arm64: Disallow combination of ARCH_XGENE and 16K page size dann frazier
2016-01-27 23:10 ` dann frazier
2016-01-28 10:34 ` Catalin Marinas
2016-01-28 10:34 ` Catalin Marinas
2016-01-28 11:08 ` Will Deacon
2016-01-28 11:08 ` Will Deacon
2016-01-28 11:20 ` Mark Rutland
2016-01-28 11:20 ` Mark Rutland
2016-01-28 14:50 ` Jeremy Linton [this message]
2016-01-28 14:50 ` Jeremy Linton
2016-01-28 11:27 ` Suzuki K. Poulose
2016-01-28 11:27 ` Suzuki K. Poulose
2016-01-28 11:30 ` Ard Biesheuvel
2016-01-28 11:30 ` Ard Biesheuvel
2016-01-28 11:34 ` Suzuki K. Poulose
2016-01-28 11:34 ` Suzuki K. Poulose
2016-01-28 11:24 ` Mark Rutland
2016-01-28 11:24 ` Mark Rutland
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=56AA2A9C.5080602@arm.com \
--to=jeremy.linton@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.