From: David Mosberger <davidm@napali.hpl.hp.com>
To: "Seth, Rohit" <rohit.seth@intel.com>
Cc: "David S. Miller" <davem@davemloft.net>,
linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org,
davidm@hpl.hp.com
Subject: RE: [patch] arch hook for notifying changes in PTE protections bits
Date: Sat, 19 Mar 2005 20:30:05 +0000 [thread overview]
Message-ID: <16956.35789.229286.442052@napali.hpl.hp.com> (raw)
In-Reply-To: <01EF044AAEE12F4BAAD955CB75064943033468DE@scsmsx401.amr.corp.intel.com>
>>>>> On Sat, 19 Mar 2005 12:22:20 -0800, "Seth, Rohit" <rohit.seth@intel.com> said:
Rohit> David S. Miller <mailto:davem@davemloft.net> wrote on Friday,
Rohit> March 18, 2005 8:06 PM:
>> Take a look at set_pte_at(). You get the "mm", the virtual
>> address, the pte pointer, and the new pte value.
Rohit> Thanks for pointing out the updated interface in 2.6.12-*
Rohit> kernel. I think I can overload the arch specific part of
Rohit> set_pte_at(or for that matter set_pte, as what I need is only
Rohit> pte_t) to always check if we need to do lazy I/D coherency
Rohit> for IA-64.....but this incurs extra cost for making a check
Rohit> every time set_pte_at is called. This new hook,
Rohit> lazy_mmu_prot_update, though needs to be used only when the
Rohit> permissions on a valid PTE is changing. For example, at the
Rohit> time of remap or swap, this API is not called.
Careful though: not every PTE has an associated page_map entry.
I agree about your concern about cost. Accessing the page_map is
expensive (integer division + memory access) and we have to do that in
order to find out if the page is i-cache clean.
--david
next prev parent reply other threads:[~2005-03-19 20:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050318162943.A3157@unix-os.sc.intel.com>
2005-03-19 4:05 ` [patch] arch hook for notifying changes in PTE protections bits David S. Miller
2005-03-19 20:22 ` Seth, Rohit
2005-03-19 20:30 ` David Mosberger [this message]
2005-03-20 0:27 ` David S. Miller
2005-03-20 22:38 ` Seth, Rohit
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=16956.35789.229286.442052@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=davem@davemloft.net \
--cc=davidm@hpl.hp.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rohit.seth@intel.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