Messages in this thread | | | Date | Mon, 3 Nov 2003 16:41:16 -0800 | From | "David S. Miller" <> | Subject | Re: virt_to_page/pci_map_page vs. pci_map_single |
| |
On Mon, 3 Nov 2003 14:02:57 -0800 David Mosberger <davidm@napali.hpl.hp.com> wrote:
> >>>>> On 03 Nov 2003 09:17:59 -0500, Jes Sorensen <jes@wildopensource.com> said: > > 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.
That's correct and it'll break on sparc64 for similar reasons.
It's also not safe to do virt_to_page() on kernel stack addresses either. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |