From: Dave Hansen <haveblue@us.ibm.com>
To: Ian Pratt <Ian.Pratt@cl.cam.ac.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>,
Keir.Fraser@cl.cam.ac.uk, Christian.Limpach@cl.cam.ac.uk
Subject: Re: [patch 4/4] Xen core patch : /dev/mem calls io_remap_page_range
Date: Wed, 17 Nov 2004 17:20:28 -0800 [thread overview]
Message-ID: <1100740828.12373.269.camel@localhost> (raw)
In-Reply-To: <E1CUajU-0005vu-00@mta1.cl.cam.ac.uk>
On Wed, 2004-11-17 at 17:05, Ian Pratt wrote:
> If there really are no uses, an alternative patch would be to
> introduce an ARCH_HAS_REMAP_PAGE_RANGE. Would this be preferable?
Well, first of all, remap_page_range() is now deprecated, so some of
this might not even be relevant. :)
My only worry is that you might want *all* calls to
remap_page/pfn_range() to be to io_remap_page/pfn_range() for your
arch. If this isn't the case, then there really isn't an issue. And,
yes, mem.c is a mess.
Thanks for the explanation.
-- Dave
next prev parent reply other threads:[~2004-11-18 1:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-17 23:56 [patch 4/4] Xen core patch : /dev/mem calls io_remap_page_range Ian Pratt
2004-11-18 0:25 ` Dave Hansen
2004-11-18 1:05 ` Ian Pratt
2004-11-18 1:20 ` Dave Hansen [this message]
2004-11-18 3:01 ` Andrew Morton
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=1100740828.12373.269.camel@localhost \
--to=haveblue@us.ibm.com \
--cc=Christian.Limpach@cl.cam.ac.uk \
--cc=Ian.Pratt@cl.cam.ac.uk \
--cc=Keir.Fraser@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