From: David Mosberger <davidm@napali.hpl.hp.com>
To: Jes Sorensen <jes@wildopensource.com>
Cc: Jamie Wellnitz <Jamie.Wellnitz@emulex.com>, linux-kernel@vger.kernel.org
Subject: Re: virt_to_page/pci_map_page vs. pci_map_single
Date: Mon, 3 Nov 2003 14:02:57 -0800 [thread overview]
Message-ID: <16294.53393.763572.291298@napali.hpl.hp.com> (raw)
In-Reply-To: <yq0sml5a63s.fsf@wildopensource.com>
>>>>> On 03 Nov 2003 09:17:59 -0500, Jes Sorensen <jes@wildopensource.com> said:
>>>>> "Jamie" == Jamie Wellnitz <Jamie.Wellnitz@emulex.com> writes:
Jamie> On Mon, Nov 03, 2003 at 03:10:46AM -0500, Jes Sorensen wrote:
>>> virt_to_page() can handle any page in the standard kernel region
Jamie> What is the "standard kernel region"? ZONE_NORMAL?
Jes> Hmmm, my brain has gotten ia64ified ;-) It's basically the normal
Jes> mappings of the kernel, ie. the kernel text/data/bss segments as well
Jes> as anything you do not get back as a dynamic mapping such as
Jes> ioremap/vmalloc/kmap.
I don't think it's safe to use virt_to_page() on static kernel
addresses (text, data, and bss). For example, ia64 linux nowadays
uses a virtual mapping for the static kernel memory, so it's not part
of the identity-mapped segment.
--david
next prev parent reply other threads:[~2003-11-03 22:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-02 18:12 virt_to_page/pci_map_page vs. pci_map_single Jamie Wellnitz
2003-11-03 8:10 ` Jes Sorensen
2003-11-03 12:52 ` Jamie Wellnitz
2003-11-03 14:17 ` Jes Sorensen
2003-11-03 22:02 ` David Mosberger [this message]
2003-11-04 0:41 ` David S. Miller
2003-11-04 9:44 ` Jes Sorensen
2003-11-03 18:48 James Bottomley
2003-11-03 22:03 ` Jamie Wellnitz
2003-11-04 9:48 ` Jes Sorensen
2003-11-04 16:35 ` Matt Porter
2003-11-04 16:47 ` James Bottomley
2003-11-04 17:11 ` Matt Porter
2003-11-04 16:43 ` James Bottomley
2003-11-05 16:23 ` Anton Blanchard
2003-11-06 8:28 ` Jes Sorensen
[not found] <NuZH.1a5.7@gated-at.bofh.it>
[not found] ` <NI6s.1MM.3@gated-at.bofh.it>
[not found] ` <NMtC.7Vs.21@gated-at.bofh.it>
[not found] ` <NNSy.1Cd.1@gated-at.bofh.it>
[not found] ` <NV3O.5w7.19@gated-at.bofh.it>
[not found] ` <NWCA.7Qv.19@gated-at.bofh.it>
2003-11-04 8:41 ` Ihar 'Philips' Filipau
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=16294.53393.763572.291298@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=Jamie.Wellnitz@emulex.com \
--cc=davidm@hpl.hp.com \
--cc=jes@wildopensource.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;
as well as URLs for NNTP newsgroup(s).