All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: "Kirill A. Shutemov" <kirill@shutemov.name>
Cc: Heiko Carstens <heiko.carstens@de.ibm.com>, linux-mm@kvack.org
Subject: Re: TLB flushes on s390
Date: Wed, 6 May 2015 14:56:40 +0200	[thread overview]
Message-ID: <20150506145640.70ee8686@mschwide> (raw)
In-Reply-To: <20150506125000.GB17739@node.dhcp.inet.fi>

On Wed, 6 May 2015 15:50:00 +0300
"Kirill A. Shutemov" <kirill@shutemov.name> wrote:

> On Wed, May 06, 2015 at 02:00:02PM +0200, Martin Schwidefsky wrote:
> > On Wed, 6 May 2015 14:29:39 +0300
> > "Kirill A. Shutemov" <kirill@shutemov.name> wrote:
> > 
> > > I'm looking though s390 code around page table handling and I found that
> > > in many places s390 does tlb flush before changing page table entry.
> > 
> > Uhh, have fun with that.. it is complicated :-/
> >  
> > > Let's look for instance on pmdp_clear_flush() implementation on s390.
> > > It's implemented with pmdp_get_and_clear() which does pmdp_flush_direct()
> > > *before* pmd_clear(). That's invert order comparing to generic
> > > pmdp_flush_direct().
> > > 
> > > The question is what prevents tlb from being re-fill between flushing tlb
> > > and clearing page table entry?
> >  
> > Look again at pmdp_flush_direct(), either __pmdp_idte_local or __pmdp_idte is
> > called. Both functions use the IDTE instruction but in two different flavors.
> > The mnemonic IDTE stands for invalidate-dat-table-entry, the instruction sets
> > the invalid bit in the PMD and flushes all TLB entries on all CPUs that are
> > affected by the now invalid PMD. The pmd_clear after the pmdp_flush_direct is
> > done to set all the other bits of the PMD to the "empty" state. The invalid
> > bit is already set prior to pmd_clear.
> 
> Okay, it makes some sense.
> 
> One more question: why does __tlb_flush_full()/__tlb_flush_asce() require
> disabling preemption and pmdp_flush_direct() doesn't?
 
Easy: for pmdp_flush_direct you are required to hold the pmd-lock as you
modify the pmd. The spinlock provides the preempt_disable.

-- 
blue skies,
   Martin.

"Reality continues to ruin my life." - Calvin.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

      reply	other threads:[~2015-05-06 12:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-06 11:29 TLB flushes on s390 Kirill A. Shutemov
2015-05-06 12:00 ` Martin Schwidefsky
2015-05-06 12:50   ` Kirill A. Shutemov
2015-05-06 12:56     ` Martin Schwidefsky [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=20150506145640.70ee8686@mschwide \
    --to=schwidefsky@de.ibm.com \
    --cc=heiko.carstens@de.ibm.com \
    --cc=kirill@shutemov.name \
    --cc=linux-mm@kvack.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.