From: Christoph Hellwig <hch@infradead.org>
To: Ian Pratt <Ian.Pratt@cl.cam.ac.uk>
Cc: linux-kernel@vger.kernel.org, Steven.Hand@cl.cam.ac.uk,
Christian.Limpach@cl.cam.ac.uk, Keir.Fraser@cl.cam.ac.uk,
akpm@osdl.org
Subject: Re: [1/6] Xen VMM #4: add ptep_establish_new to make va available
Date: Wed, 8 Dec 2004 10:42:56 +0000 [thread overview]
Message-ID: <20041208104256.GA29779@infradead.org> (raw)
In-Reply-To: <E1CbwFx-0006QL-00@mta1.cl.cam.ac.uk>
On Wed, Dec 08, 2004 at 07:29:01AM +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 thought we preffered DaveM's more generic patch instead of this one?
next prev parent reply other threads:[~2004-12-08 10:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-08 7:28 Xen VMM patch set - take 4 Ian Pratt
2004-12-08 7:29 ` [1/6] Xen VMM #4: add ptep_establish_new to make va available Ian Pratt
2004-12-08 10:42 ` Christoph Hellwig [this message]
2004-12-08 7:29 ` [2/6] Xen VMM #4: return code for arch_free_page Ian Pratt
2004-12-08 7:30 ` [3/6] Xen VMM #4: runtime disable of VT console Ian Pratt
2004-12-08 12:41 ` David Woodhouse
2004-12-08 7:30 ` [4/6] Xen VMM #4: HAS_ARCH_DEV_MEM Ian Pratt
2004-12-08 10:44 ` Christoph Hellwig
2004-12-08 7:31 ` [5/6] Xen VMM #4: split free_irq into teardown_irq Ian Pratt
2004-12-08 7:31 ` [6/6] Xen VMM #4: alloc_skb_from_cache Ian Pratt
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=20041208104256.GA29779@infradead.org \
--to=hch@infradead.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=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