Received-SPF: pass (google.com: domain of linux-kernel+bounces-151038-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.80.249 as permitted sender) client-ip=147.75.80.249;
Date: Fri, 19 Apr 2024 15:06:59 +0900
From: Byungchul Park <byungchul@sk.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	kernel_team@skhynix.com, akpm@linux-foundation.org,
	ying.huang@intel.com, vernhao@tencent.com,
	mgorman@techsingularity.net, hughd@google.com, willy@infradead.org,
	david@redhat.com, peterz@infradead.org, luto@kernel.org,
	mingo@redhat.com, bp@alien8.de, dave.hansen@linux.intel.com,
	rjgolo@gmail.com
Subject: Re: [PATCH v9 1/8] x86/tlb: add APIs manipulating tlb batch's arch
 data
Message-ID: <20240419060659.GB48027@system.software.com>
References: <20240417071847.29584-2-byungchul@sk.com>
 <871q71ykvl.ffs@tglx>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <871q71ykvl.ffs@tglx>
User-Agent: Mutt/1.9.4 (2018-02-28)

On Fri, Apr 19, 2024 at 07:36:14AM +0200, Thomas Gleixner wrote:
> On Wed, Apr 17 2024 at 16:18, Byungchul Park wrote:
> > This is a preparation for migrc mechanism that needs to recognize
> > read-only tlb entries during migration by separating tlb batch arch data
> > into two, one is for read-only entries and the other is for writable
> > ones, and merging those two when needed.
> 
> I have no idea what migrc mechanism means. Please add enough context
> into the change log so the reviewer does not have to go through loops
> and hoops to figure out what this is about.

I will add a simple description explaining 'what migrc is' at every
patch mentioning migrc, from the next spin.  Thank you for the advice.

JFYI, you can see what migrc is in the following link:

   https://lore.kernel.org/lkml/20240418061536.11645-1-byungchul@sk.com/

	Byungchul

> Thanks,
> 
>         tglx