virt_to_page/pci_map_page vs. pci_map_single
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
Hi!
Can any-one draw a conclusion?
Which function should be used in which case?
So this will be at least reflected in lkml archives ;-)
Quoted 22 lines · David S. Miller
Quoted 11 lines · On Mon, 3 Nov 2003 14:02:57 -0800 David Mosberger <[email protected]>…
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line · Jes Sorensen
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.
Signature · 5 lines
Ihar 'Philips' Filipau / with best regards from Saarbruecken.
-- _ _ _
"... and for $64000 question, could you get yourself |_|*|_|
vaguely familiar with the notion of on-topic posting?" |_|_|*|
-- Al Viro @ LKML |*|*|*|