All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Tim Chen <tim.c.chen@linux.intel.com>
Cc: stable@vger.kernel.org, Andy Lutomirski <luto@kernel.org>,
	Nadav Amit <nadav.amit@gmail.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	Arjan van de Ven <arjan@linux.intel.com>,
	Borislav Petkov <bp@alien8.de>,
	Dave Hansen <dave.hansen@intel.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Mel Gorman <mgorman@suse.de>,
	Peter Zijlstra <peterz@infradead.org>,
	Rik van Riel <riel@redhat.com>, Ingo Molnar <mingo@kernel.org>,
	David Woodhouse <dwmw@amazon.co.uk>,
	ak@linux.intel.com, karahmed@amazon.de, pbonzini@redhat.com,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] x86/mm: Give each mm a unique ID
Date: Fri, 9 Mar 2018 17:14:35 -0800	[thread overview]
Message-ID: <20180310011435.GA27284@kroah.com> (raw)
In-Reply-To: <8322b21f-5ee7-41a6-7897-d73faa0ece27@linux.intel.com>

On Fri, Mar 09, 2018 at 05:04:39PM -0800, Tim Chen wrote:
> On 03/08/2018 10:23 AM, Tim Chen wrote:
> > On 03/07/2018 09:30 AM, Greg Kroah-Hartman wrote:
> >> On Fri, Mar 02, 2018 at 01:32:09PM -0800, Tim Chen wrote:
> >>> From: Andy Lutomirski <luto@kernel.org>
> >>> commit: f39681ed0f48498b80455095376f11535feea332
> >>>
> >>> This adds a new variable to mmu_context_t: ctx_id.
> >>> ctx_id uniquely identifies the mm_struct and will never be reused.
> >>>
> >>> Signed-off-by: Andy Lutomirski <luto@kernel.org>
> >>> Reviewed-by: Nadav Amit <nadav.amit@gmail.com>
> >>> Reviewed-by: Thomas Gleixner <tglx@linutronix.de>
> >>> Cc: Andrew Morton <akpm@linux-foundation.org>
> >>> Cc: Arjan van de Ven <arjan@linux.intel.com>
> >>> Cc: Borislav Petkov <bp@alien8.de>
> >>> Cc: Dave Hansen <dave.hansen@intel.com>
> >>> Cc: Linus Torvalds <torvalds@linux-foundation.org>
> >>> Cc: Mel Gorman <mgorman@suse.de>
> >>> Cc: Peter Zijlstra <peterz@infradead.org>
> >>> Cc: Rik van Riel <riel@redhat.com>
> >>> Cc: linux-mm@kvack.org
> >>> Link: http://lkml.kernel.org/r/413a91c24dab3ed0caa5f4e4d017d87b0857f920.1498751203.git.luto@kernel.org
> >>> Signed-off-by: Ingo Molnar <mingo@kernel.org>
> >>> Signed-off-by: Tim Chen <tim.c.chen@linux.intel.com>
> >>> ---
> >>>  arch/x86/include/asm/mmu.h         | 15 +++++++++++++--
> >>>  arch/x86/include/asm/mmu_context.h |  5 +++++
> >>>  arch/x86/mm/tlb.c                  |  2 ++
> >>>  3 files changed, 20 insertions(+), 2 deletions(-)
> >>>
> >>
> >> Does not apply to 4.4.y :(
> >>
> >> Can you provide a working backport for that tree?
> >>
> > 
> > Okay. Will do.  Thanks.
> > 
> 
> 
> Greg,
> 
> I actually found that there are a number of dependent IBPB related patches that haven't been
> backported yet to 4.4:
> 
>     x86/cpufeatures: Add AMD feature bits for Speculation Control
>     (cherry picked from commit 5d10cbc91d9eb5537998b65608441b592eec65e7)
> 
>     x86/msr: Add definitions for new speculation control MSRs
>     (cherry picked from commit 1e340c60d0dd3ae07b5bedc16a0469c14b9f3410)
> 
>     x86/speculation: Add basic IBPB (Indirect Branch Prediction Barrier) support
>     (cherry picked from commit 20ffa1caecca4db8f79fe665acdeaa5af815a24d)
> 
>     x86/cpufeatures: Clean up Spectre v2 related CPUID flags
>     (cherry picked from commit 2961298efe1ea1b6fc0d7ee8b76018fa6c0bcef2)
> 
> And probably and a few more.
> You have plans to backport these patches?

I don't, but I think someone from Amazon was looking into it, but I
haven't heard from them in a few weeks.  I'll gladly take patches if you
have them, or at the worse case, a list like above of the git commits
that are missing.

thanks,

greg k-h

  reply	other threads:[~2018-03-10  1:14 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-02 21:32 [PATCH 0/2] Backport IBPB on context switch to non-dumpable process Tim Chen
2018-03-02 21:32 ` Tim Chen
2018-03-02 21:32 ` [PATCH 1/2] x86/mm: Give each mm a unique ID Tim Chen
2018-03-02 21:32   ` Tim Chen
2018-03-07 17:30   ` Greg Kroah-Hartman
2018-03-07 17:30     ` Greg Kroah-Hartman
2018-03-08 18:23     ` Tim Chen
2018-03-10  1:04       ` Tim Chen
2018-03-10  1:14         ` Greg Kroah-Hartman [this message]
2018-03-02 21:32 ` [PATCH 2/2] x86/speculation: Use Indirect Branch Prediction Barrier in context switch Tim Chen
2018-03-02 21:32   ` Tim Chen
2018-03-02 21:32   ` Tim Chen
2018-03-03  8:54 ` [PATCH 0/2] Backport IBPB on context switch to non-dumpable process Greg Kroah-Hartman
2018-03-03  8:54   ` Greg Kroah-Hartman
2018-03-03 11:37   ` Woodhouse, David
2018-03-03 11:37     ` Woodhouse, David
2018-03-07 17:32 ` Greg Kroah-Hartman
2018-03-07 17:32   ` Greg Kroah-Hartman

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=20180310011435.GA27284@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=ak@linux.intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=arjan@linux.intel.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@intel.com \
    --cc=dwmw@amazon.co.uk \
    --cc=karahmed@amazon.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=luto@kernel.org \
    --cc=mgorman@suse.de \
    --cc=mingo@kernel.org \
    --cc=nadav.amit@gmail.com \
    --cc=pbonzini@redhat.com \
    --cc=peterz@infradead.org \
    --cc=riel@redhat.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.