linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Joakim Tjernlund" <Joakim.Tjernlund@lumentis.se>
To: <paulus@samba.org>
Cc: "Linuxppc-Dev@Lists. Linuxppc. Org" <linuxppc-dev@lists.linuxppc.org>
Subject: Re: _PAGE_HWWRITE missing in pte_mkdirty()?
Date: Sun, 27 Apr 2003 11:31:58 +0200	[thread overview]
Message-ID: <001701c30c9f$dc8ae790$020120b0@jockeXP> (raw)
In-Reply-To: 16043.7040.957962.917725@nanango.paulus.ozlabs.org


> Joakim Tjernlund writes:
>
> > OK, I wasn't aware that you can have dirty pages without _PAGE_RW.
>
> Yes, think about what happens if a process has a writable dirty page
> (in a private or anonymous mapping) and the process does a fork.  The
> page becomes copy-on-write, so we have to make it non-writable, but it
> is still dirty.

Yes, that makes sense. Thanks.

> Whether the kernel actually ever calls pte_mkdirty on a non-writable
> page is a different question, of course. :)

I don't think the kernel calls pte_mkdirty in this case. I tried it on my mpc862 system and it worked fine.
I was just trying to avoid DTLB errors.

   Jocke

PS.
  Could comment on my previous post about cacheable_memcpy() as well?
  http://lists.linuxppc.org/linuxppc-dev/200304/msg00057.html

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

      reply	other threads:[~2003-04-27  9:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-25 10:33 _PAGE_HWWRITE missing in pte_mkdirty()? Joakim Tjernlund
2003-04-25 14:56 ` Dan Malek
2003-04-25 15:34   ` Joakim Tjernlund
2003-04-26 23:51     ` Paul Mackerras
2003-04-27  9:31       ` Joakim Tjernlund [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='001701c30c9f$dc8ae790$020120b0@jockeXP' \
    --to=joakim.tjernlund@lumentis.se \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=paulus@samba.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 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).