Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: vladimir.murzin@arm.com (Vladimir Murzin)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/3] Support Common Not Private translations
Date: Fri, 18 May 2018 10:59:27 +0100	[thread overview]
Message-ID: <981db1e7-687a-93a9-bea2-1fadcf5a4bd8@arm.com> (raw)
In-Reply-To: <1526636765-11289-1-git-send-email-vladimir.murzin@arm.com>

On 18/05/18 10:46, Vladimir Murzin wrote:
> Common Not Private (CNP) translations is a feature of ARMv8.2
> extension which allows translation table entries to be shared between
> different PEs in the same inner shareable domain, so the hardware can
> use this fact to optimise the caching of such entries in the TLB.
> 
> This patch set is an attempt to bring CNP support into Linux. It was
> tested on a v8.2 Fast Model with exploring traces and checking that
> TTBRx_ELy and VTTBR_EL2 have CnP bit set where appropriate.
> 
> Changelog:
> 
> 	 v2 -> v3
> 	    - do not enable CNP if we are crush kernel (per James)
> 	    - default to "no"
> 	    - rebased on 4.17-rc4

Please, ignore it - it was generated from outdated branch. I'll resend
shortly.

Thanks
Vladimir

> 
>   	 v1 -> v2
>             - handle cpuilde case (per James)
> 	    - use lm_allias with swapper_pg_dir (per James)
>             - rule out ARM64_SW_TTBR0_PAN case (per Catalin)
> 	    - s/BUG_ON/WARN_ON/ (per Catalin)
> 	    - comment and commit message updates (per Catalin)
> 	    - TTBR_CNP_BIT moved to asm/pgtable-hwdef.h (per Catalin)
> 	    - has_useable_cnp() simplified (per Julien)
> 
> 	RFC -> v1
>             - dropped RFC tag
>             - rebased on 4.14-rc4
> 
> Thanks!
> 
> Vladimir Murzin (3):
>   arm64: mm: Support Common Not Private translations
>   arm64: KVM: Enable Common Not Private translations
>   arm64: Introduce command line parameter to disable CNP
> 
>  Documentation/admin-guide/kernel-parameters.txt |  4 +++
>  arch/arm/include/asm/kvm_mmu.h                  |  5 ++++
>  arch/arm64/Kconfig                              | 13 ++++++++
>  arch/arm64/include/asm/cpucaps.h                |  3 +-
>  arch/arm64/include/asm/cpufeature.h             |  6 ++++
>  arch/arm64/include/asm/kvm_mmu.h                |  5 ++++
>  arch/arm64/include/asm/mmu_context.h            | 12 ++++++++
>  arch/arm64/include/asm/pgtable-hwdef.h          |  2 ++
>  arch/arm64/kernel/cpufeature.c                  | 40 +++++++++++++++++++++++++
>  arch/arm64/kernel/hibernate.c                   |  2 +-
>  arch/arm64/kernel/suspend.c                     |  4 +++
>  arch/arm64/kvm/hyp-init.S                       |  3 ++
>  arch/arm64/mm/context.c                         |  3 ++
>  arch/arm64/mm/proc.S                            |  6 ++++
>  virt/kvm/arm/arm.c                              |  4 +--
>  15 files changed, 108 insertions(+), 4 deletions(-)
> 

      parent reply	other threads:[~2018-05-18  9:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-18  9:46 [PATCH v3 0/3] Support Common Not Private translations Vladimir Murzin
2018-05-18  9:46 ` [PATCH v3 1/3] arm64: mm: " Vladimir Murzin
2018-05-18  9:46 ` [PATCH v3 2/3] arm64: KVM: Enable " Vladimir Murzin
2018-05-18  9:46 ` [PATCH v3 3/3] arm64: Introduce command line parameter to disable CNP Vladimir Murzin
2018-05-18  9:59 ` Vladimir Murzin [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=981db1e7-687a-93a9-bea2-1fadcf5a4bd8@arm.com \
    --to=vladimir.murzin@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox