Linux PARISC architecture development
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: Helge Deller <deller@gmx.de>,
	John David Anglin <dave.anglin@bell.net>,
	linux-parisc@vger.kernel.org
Subject: Re: [PATCH] parisc: use per-pagetable spinlock
Date: Sat, 06 Apr 2019 14:28:52 -0700	[thread overview]
Message-ID: <1554586132.5053.14.camel@HansenPartnership.com> (raw)
In-Reply-To: <alpine.LRH.2.02.1904061635090.31596@file01.intranet.prod.int.rdu2.redhat.com>

On Sat, 2019-04-06 at 16:40 -0400, Mikulas Patocka wrote:
> 
> On Sat, 6 Apr 2019, James Bottomley wrote:
> 
> > On Sat, 2019-04-06 at 16:13 -0400, Mikulas Patocka wrote:
> > > 
> > > > Of course, on systems without a merced bus, we don't need the
> lock
> > > at 
> > > > all, so runtime patching might be usable to fix that case.
> > > > 
> > > > James
> > > 
> > > The lock is still needed to synchronize TLB fault handlers with
> the
> > > code that modifies the pagetables - but we could have per-process
> > > lock for this purpose.
> > 
> > It is?  I don't think we need any per-arch sync for that.  The
> purge
> > should happen after all modifications are done so the next page
> fault
> > inserts the new TLB entry ... so if there is a place where the
> purge
> > lock matters to the page table updates, we're doing something
> wrong.
> > 
> > James
> 
> Suppose that this sequence happens:
> 
> CPU1:
> (inside the TLB miss handler)
> read the value XXX from the pagetables to the register
> 
> CPU2:
> modify the value in the pagetables to YYY
> broadcast a TLB purge
> 
> CPU1:
> receives the TLB purge broadcast and flushes the TLB
> ... continues executing the TLB handler and inserts the value XXX
> from the register into the TLB
> 
> And now, CPU1 is running with stale entry in the TLB. We need the
> lock to prevent this situation.

Heh, this is the dreaded appendix F.  In general, if we're executing a
high priority interruption for a TLB miss, the address is termed relied
upon, so a purge for the same address won't be acted upon and
acknowledged by the CPU until we leave the high priority handler (and
have thus either inserted a TLB entry or dropped into full fault
handling).  This effectively makes the purge and the insertion atomic
with respect to each other as they would be if the CPU had a hardware
TLB miss handler.  In the worst case, the CPU refaults on the same
address because it got inserted then purged and the new translation
then gets inserted second time around.

James


  reply	other threads:[~2019-04-06 21:28 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-06 19:36 [PATCH] parisc: use per-pagetable spinlock Mikulas Patocka
2019-04-06 19:49 ` James Bottomley
2019-04-06 20:13   ` Mikulas Patocka
2019-04-06 20:32     ` James Bottomley
2019-04-06 20:40       ` Mikulas Patocka
2019-04-06 21:28         ` James Bottomley [this message]
2019-04-07 17:07           ` Mikulas Patocka
2019-04-10 15:05         ` John David Anglin
2019-04-10 16:09           ` Mikulas Patocka
     [not found]             ` <e81cc4d8-0da9-454b-6102-c89bb5cdd0b0@bell.net>
2019-04-11 13:18               ` John David Anglin
2019-04-06 20:15   ` Helge Deller
2019-04-07  2:48     ` James Bottomley
2019-04-07 17:23       ` Mikulas Patocka
2019-04-07 17:42         ` James Bottomley
2019-04-10 19:10   ` John David Anglin
2019-04-10 19:27     ` John David Anglin
2019-04-13 16:23       ` Helge Deller
2019-04-13 17:57         ` John David Anglin

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=1554586132.5053.14.camel@HansenPartnership.com \
    --to=james.bottomley@hansenpartnership.com \
    --cc=dave.anglin@bell.net \
    --cc=deller@gmx.de \
    --cc=linux-parisc@vger.kernel.org \
    --cc=mpatocka@redhat.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