From: Greg KH <gregkh@linuxfoundation.org>
To: Tim Chen <tim.c.chen@linux.intel.com>
Cc: luto@kernel.org, akpm@linux-foundation.org,
arjan@linux.intel.com, bp@alien8.de, dave.hansen@intel.com,
mgorman@suse.de, mingo@kernel.org, nadav.amit@gmail.com,
peterz@infradead.org, riel@redhat.com, tglx@linutronix.de,
torvalds@linux-foundation.org, stable@vger.kernel.org,
stable-commits@vger.kernel.org
Subject: Re: Patch "x86/mm: Give each mm TLB flush generation a unique ID" has been added to the 4.9-stable tree
Date: Thu, 8 Mar 2018 10:35:58 -0800 [thread overview]
Message-ID: <20180308183558.GA16984@kroah.com> (raw)
In-Reply-To: <ad978cb3-10be-3cc9-130b-e98e91c73a5f@linux.intel.com>
On Thu, Mar 08, 2018 at 10:27:56AM -0800, Tim Chen wrote:
> On 03/07/2018 09:37 AM, gregkh@linuxfoundation.org wrote:
> >
> > This is a note to let you know that I've just added the patch titled
> >
> > x86/mm: Give each mm TLB flush generation a unique ID
> >
> > to the 4.9-stable tree which can be found at:
> > http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> >
> > The filename of the patch is:
> > x86-mm-give-each-mm-tlb-flush-generation-a-unique-id.patch
> > and it can be found in the queue-4.9 subdirectory.
> >
> > If you, or anyone else, feels it should not be added to the stable tree,
> > please let <stable@vger.kernel.org> know about it.
> >
> >
> > From f39681ed0f48498b80455095376f11535feea332 Mon Sep 17 00:00:00 2001
> > From: Andy Lutomirski <luto@kernel.org>
> > Date: Thu, 29 Jun 2017 08:53:15 -0700
> > Subject: x86/mm: Give each mm TLB flush generation a unique ID
> >
> > From: Andy Lutomirski <luto@kernel.org>
> >
> > commit f39681ed0f48498b80455095376f11535feea332 upstream.
> >
> > This adds two new variables to mmu_context_t: ctx_id and tlb_gen.
> > ctx_id uniquely identifies the mm_struct and will never be reused.
> > For a given mm_struct (and hence ctx_id), tlb_gen is a monotonic
>
> Greg, I've only pulled the unique ctx_id part of the original patch and not the
> tlb_gen changes. The unique ctx_id is a very simple change
> without needing other related changes that tlb_gen will require.
>
> You may want to update the comment to reflect this.
I try to keep the commit text identical, but am willing to add a note at
the top or usually, the bottom of the text to show what changed in the
specific stable patch. Can you give me some text that I can put there
to reflect what you changed here?
thanks,
greg k-h
prev parent reply other threads:[~2018-03-08 18:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-07 17:37 Patch "x86/mm: Give each mm TLB flush generation a unique ID" has been added to the 4.9-stable tree gregkh
2018-03-08 18:27 ` Tim Chen
2018-03-08 18:35 ` Greg KH [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=20180308183558.GA16984@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=arjan@linux.intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@intel.com \
--cc=luto@kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@kernel.org \
--cc=nadav.amit@gmail.com \
--cc=peterz@infradead.org \
--cc=riel@redhat.com \
--cc=stable-commits@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=tim.c.chen@linux.intel.com \
--cc=torvalds@linux-foundation.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