From: Peter Zijlstra <peterz@infradead.org>
To: Nadav Amit <namit@vmware.com>
Cc: Yang Shi <yang.shi@linux.alibaba.com>,
"jstancek@redhat.com" <jstancek@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
Linux-MM <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
"Aneesh Kumar K . V" <aneesh.kumar@linux.vnet.ibm.com>,
Nick Piggin <npiggin@gmail.com>, Minchan Kim <minchan@kernel.org>,
Mel Gorman <mgorman@suse.de>, Will Deacon <will.deacon@arm.com>
Subject: Re: [PATCH] mm: mmu_gather: remove __tlb_reset_range() for force flush
Date: Mon, 13 May 2019 13:30:06 +0200 [thread overview]
Message-ID: <20190513113006.GP2623@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <75FD46B2-2E0C-41F2-9308-AB68C8780E33@vmware.com>
On Mon, May 13, 2019 at 09:11:38AM +0000, Nadav Amit wrote:
> BTW: sometimes you don’t see the effect of these full TLB flushes as much in
> VMs. I encountered a strange phenomenon at the time - INVLPG for an
> arbitrary page cause my Haswell machine flush the entire TLB, when the
> INVLPG was issued inside a VM. It took me quite some time to analyze this
> problem. Eventually Intel told me that’s part of what is called “page
> fracturing” - if the host uses 4k pages in the EPT, they (usually) need to
> flush the entire TLB for any INVLPG. That’s happens since they don’t know
> the size of the flushed page.
Cute... if only they'd given us an interface to tell them... :-)
next prev parent reply other threads:[~2019-05-13 11:30 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-07 21:34 [PATCH] mm: mmu_gather: remove __tlb_reset_range() for force flush Yang Shi
2019-05-09 8:37 ` Will Deacon
2019-05-09 10:38 ` Peter Zijlstra
2019-05-09 10:54 ` Peter Zijlstra
2019-05-09 18:35 ` Yang Shi
2019-05-09 18:40 ` Peter Zijlstra
2019-05-09 12:44 ` Jan Stancek
2019-05-09 17:36 ` Nadav Amit
2019-05-09 18:24 ` Peter Zijlstra
2019-05-09 19:10 ` Yang Shi
2019-05-09 21:06 ` Jan Stancek
2019-05-09 21:48 ` Yang Shi
2019-05-09 22:12 ` Jan Stancek
[not found] ` <04668E51-FD87-4D53-A066-5A35ABC3A0D6@vmware.com>
[not found] ` <20190509191120.GD2623@hirez.programming.kicks-ass.net>
2019-05-09 21:21 ` Nadav Amit
2019-05-13 8:36 ` Peter Zijlstra
2019-05-13 9:11 ` Nadav Amit
2019-05-13 11:30 ` Peter Zijlstra [this message]
2019-05-13 16:37 ` Will Deacon
2019-05-13 17:06 ` Nadav Amit
2019-05-14 8:58 ` Mel Gorman
2019-05-13 9:12 ` Peter Zijlstra
2019-05-13 9:21 ` Nadav Amit
2019-05-13 11:27 ` Peter Zijlstra
2019-05-13 17:41 ` Nadav Amit
2019-05-09 18:22 ` Yang Shi
2019-05-09 19:56 ` Peter Zijlstra
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=20190513113006.GP2623@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=jstancek@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=minchan@kernel.org \
--cc=namit@vmware.com \
--cc=npiggin@gmail.com \
--cc=stable@vger.kernel.org \
--cc=will.deacon@arm.com \
--cc=yang.shi@linux.alibaba.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).