@Shantonu - I was under the impression that IO* KPIs should only be
used by IOKit driver ?
@Mike - Virtualization. If you care to involve hypervisor in your
memory tricks then virtual address of the guest buffer is useless. You
want physical address.
@Others - I will check KPIs that you guys mention.
Seems like most device drivers that care about DMA would probably be
an IOKit driver else what I am asking for seems like very basic
On Fri, Aug 6, 2010 at 9:18 AM, Michael Smith <email@hidden> wrote:
> Why would you like to get the physical address of this buffer? What do you
> think it will tell you?
> = Mike
> On Aug 5, 2010, at 11:10 AM, shailesh jain wrote:
> Hello again!
> I have a kernel extension (which is not an IOKit driver) that uses
> OSMalloc_ KPI to allocate buffer. I pass in OSMT_DEFAULT so that
> buffers that it returns are wired to memory. I have a use case where
> in I would like
> to get physical address of the first byte of the buffer. I understand
> that buffer will not be contiguous in Physical memory and I am fine
> with that. Do we have such an interface ---
> something like: physAddr = virt_to_phys(buffer); // Gives physical
> address of first byte of the buffer
> Shailesh Jain
> Do not post admin requests to the list. They will be ignored.
> Darwin-kernel mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
> This email sent to email@hidden
> The lyf so short, the craft so long to lerne -- Chaucer
Do not post admin requests to the list. They will be ignored.
Darwin-kernel mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden