All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@linux.intel.com>
To: Andy Lutomirski <luto@kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
	 Tim Chen <tim.c.chen@linux.intel.com>,
	 Arjan van de Ven <arjan@linux.intel.com>,
	 LKML <linux-kernel@vger.kernel.org>,
	 KarimAllah Ahmed <karahmed@amazon.de>,
	 Andrea Arcangeli <aarcange@redhat.com>,
	 Ashok Raj <ashok.raj@intel.com>,
	 Asit Mallick <asit.k.mallick@intel.com>,
	 Borislav Petkov <bp@suse.de>,
	 Dan Williams <dan.j.williams@intel.com>,
	 Dave Hansen <dave.hansen@intel.com>,
	 David Woodhouse <dwmw@amazon.co.uk>,
	 Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	 "H . Peter Anvin" <hpa@zytor.com>,
	 Ingo Molnar <mingo@redhat.com>,
	 Janakarajan Natarajan <Janakarajan.Natarajan@amd.com>,
	 Joerg Roedel <joro@8bytes.org>,
	 Jun Nakajima <jun.nakajima@intel.com>
Subject: Re: [RFC PATCH 1/2] x86/ibpb: Skip IBPB when we switch back to same user process
Date: Thu, 25 Jan 2018 13:57:49 -0800	[thread overview]
Message-ID: <87h8r9k3du.fsf@linux.intel.com> (raw)
In-Reply-To: <CALCETrUGDeHse24sOygh5EcsXuZHPtZnw3adhzADfn+yKgcOzg@mail.gmail.com> (Andy Lutomirski's message of "Thu, 25 Jan 2018 13:04:23 -0800")

Andy Lutomirski <luto@kernel.org> writes:
>
> That being said, just stashing last_user_mm without any refcounting
> should be fine.

If last_user_mm is freed and reallocated by a different process,
then that would miss the IPBP incorrectly.

-Andi

  reply	other threads:[~2018-01-25 21:57 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-25  0:36 [RFC PATCH 1/2] x86/ibpb: Skip IBPB when we switch back to same user process Tim Chen
2018-01-25  0:36 ` [RFC PATCH 2/2] x86/ibpb: Prevent missed IBPB flush Tim Chen
2018-01-25  8:20   ` David Woodhouse
2018-01-25 16:56     ` Tim Chen
2018-01-25  8:58 ` [RFC PATCH 1/2] x86/ibpb: Skip IBPB when we switch back to same user process Peter Zijlstra
2018-01-25  9:22   ` Peter Zijlstra
2018-01-25 13:21     ` Arjan van de Ven
2018-01-25 13:50       ` Peter Zijlstra
2018-01-25 14:07         ` Arjan van de Ven
2018-01-25 16:41           ` Peter Zijlstra
2018-01-25 17:04             ` Andy Lutomirski
2018-01-25 18:18               ` Peter Zijlstra
2018-01-25 19:32                 ` Tim Chen
2018-01-25 19:34                   ` Arjan van de Ven
2018-01-25 19:45                     ` Dave Hansen
2018-01-25 20:46                   ` Peter Zijlstra
2018-01-25 21:04                     ` Andy Lutomirski
2018-01-25 21:57                       ` Andi Kleen [this message]
2018-01-25 22:01                         ` Andy Lutomirski
2018-01-25 23:07                           ` Tim Chen
2018-01-26  0:01                       ` Peter Zijlstra
2018-01-25 17:24             ` Arjan van de Ven

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=87h8r9k3du.fsf@linux.intel.com \
    --to=ak@linux.intel.com \
    --cc=Janakarajan.Natarajan@amd.com \
    --cc=aarcange@redhat.com \
    --cc=arjan@linux.intel.com \
    --cc=ashok.raj@intel.com \
    --cc=asit.k.mallick@intel.com \
    --cc=bp@suse.de \
    --cc=dan.j.williams@intel.com \
    --cc=dave.hansen@intel.com \
    --cc=dwmw@amazon.co.uk \
    --cc=gregkh@linuxfoundation.org \
    --cc=hpa@zytor.com \
    --cc=joro@8bytes.org \
    --cc=jun.nakajima@intel.com \
    --cc=karahmed@amazon.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=tim.c.chen@linux.intel.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 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.