From: "David S. Miller" <davem@davemloft.net>
To: "Seth, Rohit" <rohit.seth@intel.com>
Cc: 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 04:05:55 +0000 [thread overview]
Message-ID: <20050318200555.2d1980f6.davem@davemloft.net> (raw)
In-Reply-To: <20050318162943.A3157@unix-os.sc.intel.com>
This is way overkill I think.
Take a look at set_pte_at(). You get the "mm", the
virtual address, the pte pointer, and the new pte value.
What else could you possibly need to track stuff like this
and react appropriately? :-)
It is even an argument for batched TLB processing on ia64.
It simplifies a lot of cache flushing issues and you can
control the flushing on a per-translation basis however
you like.
next parent reply other threads:[~2005-03-19 4:05 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 ` David S. Miller [this message]
2005-03-19 20:22 ` [patch] arch hook for notifying changes in PTE protections bits Seth, Rohit
2005-03-19 20:30 ` David Mosberger
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=20050318200555.2d1980f6.davem@davemloft.net \
--to=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