linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Brian Cain" <bcain@codeaurora.org>
To: "'Nicholas Piggin'" <npiggin@gmail.com>, <linux-arch@vger.kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <linux-mm@kvack.org>,
	"'Arnd Bergmann'" <arnd@arndb.de>,
	<linux-hexagon@vger.kernel.org>
Subject: RE: [PATCH 07/24] hexagon: use asm-generic/mmu_context.h for no-op implementations
Date: Tue, 11 Aug 2020 13:34:52 -0500	[thread overview]
Message-ID: <037d01d6700e$1af0a580$50d1f080$@codeaurora.org> (raw)
In-Reply-To: <20200728033405.78469-8-npiggin@gmail.com>


> -----Original Message-----
> From: linux-arch-owner@vger.kernel.org <linux-arch-owner@vger.kernel.org>
> On Behalf Of Nicholas Piggin

Acked-by: Brian Cain <bcain@codeaurora.org>

 
> Cc: Brian Cain <bcain@codeaurora.org>
> Cc: linux-hexagon@vger.kernel.org
> Signed-off-by: Nicholas Piggin <npiggin@gmail.com>
> ---
>  arch/hexagon/include/asm/mmu_context.h | 33 ++++----------------------
>  1 file changed, 5 insertions(+), 28 deletions(-)
> 
> diff --git a/arch/hexagon/include/asm/mmu_context.h
> b/arch/hexagon/include/asm/mmu_context.h
> index cdc4adc0300a..81947764c47d 100644
> --- a/arch/hexagon/include/asm/mmu_context.h
> +++ b/arch/hexagon/include/asm/mmu_context.h
> @@ -15,39 +15,13 @@
>  #include <asm/pgalloc.h>
>  #include <asm/mem-layout.h>
> 
> -static inline void destroy_context(struct mm_struct *mm) -{ -}
> -
>  /*
>   * VM port hides all TLB management, so "lazy TLB" isn't very
>   * meaningful.  Even for ports to architectures with visble TLBs,
>   * this is almost invariably a null function.
> + *
> + * mm->context is set up by pgd_alloc, so no init_new_context required.
>   */
> -static inline void enter_lazy_tlb(struct mm_struct *mm,
> -	struct task_struct *tsk)
> -{
> -}
> -
> -/*
> - * Architecture-specific actions, if any, for memory map deactivation.
> - */
> -static inline void deactivate_mm(struct task_struct *tsk,
> -	struct mm_struct *mm)
> -{
> -}
> -
> -/**
> - * init_new_context - initialize context related info for new mm_struct
> instance
> - * @tsk: pointer to a task struct
> - * @mm: pointer to a new mm struct
> - */
> -static inline int init_new_context(struct task_struct *tsk,
> -					struct mm_struct *mm)
> -{
> -	/* mm->context is set up by pgd_alloc */
> -	return 0;
> -}
> 
>  /*
>   *  Switch active mm context
> @@ -74,6 +48,7 @@ static inline void switch_mm(struct mm_struct *prev,
> struct mm_struct *next,
>  /*
>   *  Activate new memory map for task
>   */
> +#define activate_mm activate_mm
>  static inline void activate_mm(struct mm_struct *prev, struct mm_struct
> *next)  {
>  	unsigned long flags;
> @@ -86,4 +61,6 @@ static inline void activate_mm(struct mm_struct *prev,
> struct mm_struct *next)
>  /*  Generic hooks for arch_dup_mmap and arch_exit_mmap  */  #include
> <asm-generic/mm_hooks.h>
> 
> +#include <asm-generic/mmu_context.h>
> +
>  #endif
> --
> 2.23.0



  reply	other threads:[~2020-08-11 18:35 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-28  3:33 [PATCH 00/24] Use asm-generic for mmu_context no-op functions Nicholas Piggin
2020-07-28  3:33 ` [PATCH 01/24] asm-generic: add generic versions of mmu context functions Nicholas Piggin
2020-07-28  4:01   ` Vineet Gupta
2020-07-28 10:37     ` Nicholas Piggin
2020-08-26 13:59     ` Nicholas Piggin
2020-07-28  5:53   ` kernel test robot
2020-07-28 23:52   ` kernel test robot
2020-07-28  3:33 ` [PATCH 02/24] alpha: use asm-generic/mmu_context.h for no-op implementations Nicholas Piggin
2020-07-28  3:33 ` [PATCH 03/24] arc: " Nicholas Piggin
2020-07-28  3:58   ` Vineet Gupta
2020-07-28  3:33 ` [PATCH 04/24] arm: " Nicholas Piggin
2020-07-28  4:14   ` Vineet Gupta
2020-08-26 14:14     ` Nicholas Piggin
2020-07-28  3:33 ` [PATCH 05/24] arm64: " Nicholas Piggin
2020-07-28  3:33 ` [PATCH 06/24] csky: " Nicholas Piggin
2020-07-28  4:09   ` Guo Ren
2020-07-28  3:33 ` [PATCH 07/24] hexagon: " Nicholas Piggin
2020-08-11 18:34   ` Brian Cain [this message]
2020-07-28  3:33 ` [PATCH 08/24] ia64: " Nicholas Piggin
2020-07-28  3:33 ` [PATCH 09/24] m68k: " Nicholas Piggin
2020-07-30  8:11   ` kernel test robot
2020-07-28  3:33 ` [PATCH 10/24] microblaze: " Nicholas Piggin
2020-07-28  3:33 ` [PATCH 11/24] mips: " Nicholas Piggin
2020-07-28  3:33 ` [PATCH 12/24] nds32: " Nicholas Piggin
2020-07-28  3:33 ` [PATCH 13/24] nios2: " Nicholas Piggin
2020-07-28  3:33 ` [PATCH 14/24] openrisc: " Nicholas Piggin
2020-07-29 11:45   ` Stafford Horne
2020-08-26 14:33     ` Nicholas Piggin
2020-07-28  3:33 ` [PATCH 15/24] parisc: " Nicholas Piggin
2020-07-28  3:33 ` [PATCH 16/24] powerpc: " Nicholas Piggin
2020-07-28  3:33 ` [PATCH 17/24] riscv: " Nicholas Piggin
2020-07-30 21:20   ` Palmer Dabbelt
2020-07-28  3:33 ` [PATCH 18/24] s390: " Nicholas Piggin
2020-07-28  3:34 ` [PATCH 19/24] sh: " Nicholas Piggin
2020-07-28  3:34 ` [PATCH 20/24] sparc: " Nicholas Piggin
2020-07-28  3:34 ` [PATCH 21/24] um: " Nicholas Piggin
2020-07-28  3:34 ` [PATCH 22/24] unicore32: " Nicholas Piggin
2020-07-28  3:34 ` [PATCH 23/24] x86: " Nicholas Piggin
2020-07-28 10:54   ` peterz
2020-07-28  3:34 ` [PATCH 24/24] xtensa: " Nicholas Piggin

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='037d01d6700e$1af0a580$50d1f080$@codeaurora.org' \
    --to=bcain@codeaurora.org \
    --cc=arnd@arndb.de \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-hexagon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=npiggin@gmail.com \
    /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).