From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Ian Pratt <Ian.Pratt@cl.cam.ac.uk>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>,
Steven.Hand@cl.cam.ac.uk, Christian.Limpach@cl.cam.ac.uk,
Keir.Fraser@cl.cam.ac.uk, Andrew Morton <akpm@osdl.org>,
"David S. Miller" <davem@redhat.com>
Subject: Re: [1/7] Xen VMM #3: add ptep_establish_new to make va available
Date: Wed, 01 Dec 2004 09:49:51 +1100 [thread overview]
Message-ID: <1101854992.5174.14.camel@gaston> (raw)
In-Reply-To: <E1CYxP0-0005Hy-00@mta1.cl.cam.ac.uk>
On Tue, 2004-11-30 at 02:06 +0000, Ian Pratt wrote:
> This patch adds 'ptep_establish_new', in keeping with the
> existing 'ptep_establish', but for use where a mapping is being
> established where there was previously none present. This
> function is useful (rather than just using set_pte) because
> having the virtual address available enables a very important
> optimisation for arch-xen. We introduce
> HAVE_ARCH_PTEP_ESTABLISH_NEW and define a generic implementation
> in asm-generic/pgtable.h, following the pattern of the existing
> ptep_establish.
I would rather move toward that patch that David Miller proposed a while
ago that makes sure the necessary infos (mm, address, ...) are always
passed to all PTE functions.
Is there also a need for ptep_establish and ptep_establish_new to be 2
different functions ?
Ben.
next prev parent reply other threads:[~2004-11-30 22:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-30 2:06 [1/7] Xen VMM #3: add ptep_establish_new to make va available Ian Pratt
2004-11-30 2:21 ` Andrea Arcangeli
2004-11-30 22:49 ` Benjamin Herrenschmidt [this message]
2004-11-30 23:05 ` Ian Pratt
2004-11-30 23:27 ` Benjamin Herrenschmidt
2004-12-01 4:01 ` David S. Miller
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=1101854992.5174.14.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=Christian.Limpach@cl.cam.ac.uk \
--cc=Ian.Pratt@cl.cam.ac.uk \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=Steven.Hand@cl.cam.ac.uk \
--cc=akpm@osdl.org \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.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