Re: [PATCH 8/9] swiotlb: support HIGHMEM in swiotlb_bus_to_virt

From: Ian Campbell
Date: Sat May 30 2009 - 09:02:40 EST

On Fri, 2009-05-29 at 08:58 -0700, Jeremy Fitzhardinge wrote:
> Ian Campbell wrote:

> > -void * __weak swiotlb_bus_to_virt(struct device *hwdev, dma_addr_t address)
> > +#ifdef CONFIG_HIGHMEM
> > +static void * swiotlb_bus_to_virt(struct device *hwdev, dma_addr_t address)
> >
> I think it would be better to put the #ifdef within the function body so
> that there's no chance of prototype-drift.

Yes, good idea.

> > +{
> > + unsigned long pfn = PFN_DOWN(dma_to_phys(hwdev, addr));
> > + void *pageaddr = page_address(pfn_to_page(pfn));
> > +
> > + if (pageaddr != NULL)
> > + return pageaddr + (addr % PAGE_SIZE);
> >
> Is there an arch-independent test to see if a pfn is considered highmem
> or not (which returns a constant on non-highmem configurations)? If so,
> then I think this could be common without having to go via a struct page.

I'm not aware of a way apart from PageHighMem -- which needs the struct
page. Highmem is a property of the zone, I think, so you have to go
through the struct page back to the zone to find out if it is high or

At first glance it looks like many of the callers of bus_to_virt
eventually end up in swiotlb_bounce which converts to a struct page
anyway. I'll take a look next week whether it makes any sense to go to
struct page further up the call chain and pass that around instead.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at