public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Manfred Spraul <manfred@colorfullife.com>
To: Jamie Lokier <lk@tantalophile.demon.co.uk>
Cc: Linus Torvalds <torvalds@transmeta.com>, linux-kernel@vger.kernel.org
Subject: Re: x86 ptep_get_and_clear question
Date: Fri, 16 Feb 2001 16:54:44 +0100	[thread overview]
Message-ID: <3A8D4D43.CF589FA0@colorfullife.com> (raw)
In-Reply-To: <3A8C499A.E0370F63@colorfullife.com> <Pine.LNX.4.10.10102151702320.12656-100000@penguin.transmeta.com> <20010216151839.A3989@pcep-jamie.cern.ch> <3A8D4045.F8F27782@colorfullife.com> <20010216162741.A4284@pcep-jamie.cern.ch>

Jamie Lokier wrote:
> 
> /* mprotect.c */
>         entry = ptep_get_and_clear(pte);
>         set_pte(pte, pte_modify(entry, newprot));
> 
> I.e. the only code with the race condition is code which explicitly
> clears the dirty bit, in vmscan.c.
> 
> Do you see any possibility of losing a dirty bit here?
>
Of course.
Just check the output after preprocessing.
It's 
	int entry;
	entry = *pte;
	entry &= ~_PAGE_CHG_MASK;
	entry |= pgprot_val(newprot)
	*pte = entry;

We need
	atomic_clear_mask (_PAGE_CHG_MASK, pte);
	atomic_set_mask (pgprot_val(newprot), *pte);

for multi threaded apps.

> If not, there's no need for the intricate "gather" or "double scan"
> schemes for mprotect() and it can stay as fast as possible.
>
Correct, but we need a platform specific "update_pte", and perhaps
update_begin, update_end hooks (empty on i386) for other archs.

--
	Manfred

  reply	other threads:[~2001-02-16 15:54 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20010215173547.A2079@pcep-jamie.cern.ch>
     [not found] ` <200102151723.JAA43255@google.engr.sgi.com>
2001-02-15 17:47   ` x86 ptep_get_and_clear question Jamie Lokier
2001-02-15 18:05     ` Kanoj Sarcar
2001-02-15 18:23     ` Kanoj Sarcar
2001-02-15 18:42       ` Jamie Lokier
2001-02-15 18:57         ` Kanoj Sarcar
2001-02-15 19:06           ` Ben LaHaise
2001-02-15 19:19             ` Kanoj Sarcar
2001-02-15 20:16               ` Linus Torvalds
2001-02-15 18:51       ` Manfred Spraul
2001-02-15 19:05         ` Kanoj Sarcar
2001-02-15 19:19           ` Jamie Lokier
2001-02-15 20:31             ` Linus Torvalds
2001-02-15 21:26               ` Manfred Spraul
2001-02-15 21:29                 ` Manfred Spraul
2001-02-16  1:21                 ` Linus Torvalds
2001-02-16 14:18                   ` Jamie Lokier
2001-02-16 14:59                     ` Manfred Spraul
2001-02-16 15:27                       ` Jamie Lokier
2001-02-16 15:54                         ` Manfred Spraul [this message]
2001-02-16 16:00                           ` Jamie Lokier
2001-02-16 16:23                             ` Manfred Spraul
2001-02-16 16:43                               ` Jamie Lokier
2001-02-16 17:12                                 ` Manfred Spraul
2001-02-16 17:20                                   ` Jamie Lokier
2001-02-16 17:36                                     ` Linus Torvalds
2001-02-16 18:49                                       ` Manfred Spraul
2001-02-16 19:00                                         ` Linus Torvalds
2001-02-16 19:02                                         ` Ben LaHaise
2001-02-16 19:32                                           ` Linus Torvalds
2001-02-16 19:42                                             ` Ben LaHaise
2001-02-16 17:37                                   ` Jamie Lokier
2001-02-16 18:04                                     ` Manfred Spraul
2001-02-16 18:09                                       ` Jamie Lokier
2001-02-16 18:36                                     ` Hugh Dickins
2001-02-16 17:29                                 ` Ben LaHaise
2001-02-16 17:38                                   ` Linus Torvalds
2001-02-16 17:44                                     ` Ben LaHaise
2001-02-16 17:59                       ` Linus Torvalds
2001-02-15 23:57               ` Jamie Lokier
2001-02-16  0:55                 ` Linus Torvalds
2001-02-15 19:07         ` Jamie Lokier

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=3A8D4D43.CF589FA0@colorfullife.com \
    --to=manfred@colorfullife.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lk@tantalophile.demon.co.uk \
    --cc=torvalds@transmeta.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