public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: catalin.marinas@arm•com (Catalin Marinas)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 7/7] Document the use of the arm64 contpte/nonconpte flags.
Date: Mon, 5 Oct 2015 17:49:24 +0100	[thread overview]
Message-ID: <20151005164924.GB5557@MBP.local> (raw)
In-Reply-To: <1443818865-19846-8-git-send-email-jeremy.linton@arm.com>

On Fri, Oct 02, 2015 at 03:47:45PM -0500, Jeremy Linton wrote:
> These flags allow the user to enable/disable the contiguous PTE
> detection and marking on the kernel command line for
> debugging purposes.
> 
> Signed-off-by: Jeremy Linton <jeremy.linton@arm•com>
> ---
>  Documentation/kernel-parameters.txt | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/Documentation/kernel-parameters.txt b/Documentation/kernel-parameters.txt
> index 22a4b68..2766290 100644
> --- a/Documentation/kernel-parameters.txt
> +++ b/Documentation/kernel-parameters.txt
> @@ -744,6 +744,10 @@ bytes respectively. Such letter suffixes can also be entirely omitted.
>  			seconds. Defaults to 10*60 = 10mins. A value of 0
>  			disables the blank timer.
>  
> +	contpte		[ARM64] Enable contiguous PTE marking for the kernel
> +			linear range. This may be disabled with nocontpte.
> +			Default: Enabled

I recall you asked the question but I didn't have the time to reply. I
don't think we need a command line option for this. In the "unlikely"
event that something is broken in hardware (or software) and we want to
disable the contiguous bit, I would rather have a Kconfig option.

-- 
Catalin

  reply	other threads:[~2015-10-05 16:49 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-02 20:47 [PATCHv2 0/7] arm64: Use contiguous PTE bit for the kernel linear mapping Jeremy Linton
2015-10-02 20:47 ` [PATCH 1/7] arm64: Add contiguous page flag shifts and constants Jeremy Linton
2015-10-02 20:47 ` [PATCH 2/7] arm64: PTE/PMD contiguous bit definition Jeremy Linton
2015-10-06 11:10   ` Catalin Marinas
2015-10-02 20:47 ` [PATCH 3/7] arm64: Macros to check/set/unset the contiguous bit Jeremy Linton
2015-10-02 20:47 ` [PATCH 4/7] arm64: Default kernel pages should be contiguous Jeremy Linton
2015-10-02 20:47 ` [PATCH 5/7] arm64: Make the kernel page dump utility aware of the CONT bit Jeremy Linton
2015-10-02 20:47 ` [PATCH 6/7] arm64: Mark kernel page ranges contiguous Jeremy Linton
2015-10-06 11:15   ` Catalin Marinas
2015-10-02 20:47 ` [PATCH 7/7] Document the use of the arm64 contpte/nonconpte flags Jeremy Linton
2015-10-05 16:49   ` Catalin Marinas [this message]
2015-10-05 18:29     ` Jeremy Linton
2015-10-06  9:42       ` Catalin Marinas
2015-10-05 17:03 ` [PATCHv2 0/7] arm64: Use contiguous PTE bit for the kernel linear mapping Catalin Marinas
2015-10-05 18:22   ` Jeremy Linton

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=20151005164924.GB5557@MBP.local \
    --to=catalin.marinas@arm$(echo .)com \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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