[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALCETrX1TJ0BBJ40Gu_TNrrdntLdeR42Erg4QMbt5HoN9DqngA@mail.gmail.com>
Date: Thu, 9 Jun 2016 10:24:18 -0700
From: Andy Lutomirski <luto@...capital.net>
To: Nadav Amit <nadav.amit@...il.com>
Cc: Andy Lutomirski <luto@...nel.org>, X86 ML <x86@...nel.org>,
LKML <linux-kernel@...r.kernel.org>,
Borislav Petkov <bp@...en8.de>,
Brian Gerst <brgerst@...il.com>,
Dave Hansen <dave.hansen@...ux.intel.com>,
Oleg Nesterov <oleg@...hat.com>,
"linux-mm@...ck.org" <linux-mm@...ck.org>
Subject: Re: [RFC 05/13] x86/mm: Add barriers and document switch_mm-vs-flush synchronization
On Fri, Jun 3, 2016 at 10:42 AM, Nadav Amit <nadav.amit@...il.com> wrote:
> Following this patch, if (current->active_mm != mm), flush_tlb_page() still
> doesn’t call smp_mb() before checking mm_cpumask(mm).
>
> In contrast, flush_tlb_mm_range() does call smp_mb().
>
> Is there a reason for this discrepancy?
Not that I can remember. Is the remote flush case likely to be racy?
--Andy
Powered by blists - more mailing lists