From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: LEROY Christophe <christophe.leroy@c-s.fr>, linuxppc-dev@ozlabs.org
Subject: Re: _PAGE_PRESENT and _PAGE_ACCESSED
Date: Wed, 27 Jul 2016 19:49:36 +1000 [thread overview]
Message-ID: <1469612976.5978.143.camel@kernel.crashing.org> (raw)
In-Reply-To: <20160726195245.Horde.xJWqCTeuxQeC7gAnGhJItg6@messagerie.si.c-s.fr>
On Tue, 2016-07-26 at 19:52 +0200, LEROY Christophe wrote:
> In ppc8xx tlbmiss handler, we consider a page valid if both
> _PAGE_PRESENT and _PAGE_ACCESSED are set.
> Is there any chance to have _PAGE_ACCESSED set and not _PAGE_PRESENT ?
> Otherwise we could simplify the handler by considering the page valid
> only when _PAGE_ACCESSED is set
When _PAGE_PRESENT is not set, the PTE becomes a swap PTE and a pile
of the other bits can be repurposed, you may want to verify if
_PAGE_ACCESSED is one of them.
Cheers,
Ben.
prev parent reply other threads:[~2016-07-27 10:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-26 17:52 _PAGE_PRESENT and _PAGE_ACCESSED LEROY Christophe
2016-07-27 9:49 ` Benjamin Herrenschmidt [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=1469612976.5978.143.camel@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--cc=christophe.leroy@c-s.fr \
--cc=linuxppc-dev@ozlabs.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).