All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Tweedie <sct@redhat.com>
To: Ben LaHaise <bcrl@redhat.com>
Cc: torvalds@transmeta.com, Ingo Molnar <mingo@redhat.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	Stephen Tweedie <sct@redhat.com>
Subject: Re: [RFC] atomic pte updates and pae changes, take 2
Date: Sat, 14 Oct 2000 14:33:09 +0100	[thread overview]
Message-ID: <20001014143309.D5813@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0010132002440.25522-100000@devserv.devel.redhat.com>; from bcrl@redhat.com on Fri, Oct 13, 2000 at 08:17:42PM -0400

Hi,

On Fri, Oct 13, 2000 at 08:17:42PM -0400, Ben LaHaise wrote:
> 
> Below is take two of the patch making pte_clear use atomic xchg in an
> effort to avoid the loss of dirty bits.  PAE no longer uses cmpxchg8 for
> updates; set_pte is two ordered long writes with a barrier.

Looks good.  The only trouble I can see left is that pte_clear() is
still using set_pte(), which doesn't work right for PAE36.  set_pte()
is setting the high word first, which is fine for installing a new pte,
but if you do that to clear a pte then you have left the old
page-present bit intact while you've removed have of the pte.
pte_clear() needs to clear the words in the other order (just as
pte_get_and_clear correctly does).

Cheers,
 Stephen
--
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.eu.org/Linux-MM/

  parent reply	other threads:[~2000-10-14 13:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-14  0:17 [RFC] atomic pte updates and pae changes, take 2 Ben LaHaise
2000-10-14  1:43 ` Linus Torvalds
2000-10-14  8:26   ` David S. Miller
2000-10-15 12:07   ` Ingo Molnar
2000-10-14 13:33 ` Stephen Tweedie [this message]
2000-10-15 12:01   ` Ingo Molnar
2000-10-19 20:16 ` oopses in test10-pre4 (was Re: [RFC] atomic pte updates and pae changes, take 3) Linus Torvalds
2000-10-20  5:44   ` Ben LaHaise
2000-10-20 17:18     ` Linus Torvalds

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=20001014143309.D5813@redhat.com \
    --to=sct@redhat.com \
    --cc=bcrl@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mingo@redhat.com \
    --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 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.