On Wed, 23 Oct 2013, Konrad Rzeszutek Wilk wrote:
> On Wed, Oct 23, 2013 at 06:34:13PM +0100, Stefano Stabellini wrote:
> > > On Thu, Oct 17, 2013 at 06:43:33PM +0100, Stefano Stabellini wrote:
> > > > xen_unmap_single calls xen_bus_to_phys, then passes dev_addr to
> > > > is_xen_swiotlb_buffer
On Wed, 23 Oct 2013, Konrad Rzeszutek Wilk wrote:
On Wed, Oct 23, 2013 at 06:34:13PM +0100, Stefano Stabellini wrote:
On Thu, Oct 17, 2013 at 06:43:33PM +0100, Stefano Stabellini wrote:
xen_unmap_single calls xen_bus_to_phys, then passes dev_addr to
is_xen_swiotlb_buffer that calls
On Wed, Oct 23, 2013 at 06:34:13PM +0100, Stefano Stabellini wrote:
> > On Thu, Oct 17, 2013 at 06:43:33PM +0100, Stefano Stabellini wrote:
> > > xen_unmap_single calls xen_bus_to_phys, then passes dev_addr to
> > > is_xen_swiotlb_buffer that calls xen_bus_to_phys again.
> >
> > It does?
> >
> >
> On Thu, Oct 17, 2013 at 06:43:33PM +0100, Stefano Stabellini wrote:
> > xen_unmap_single calls xen_bus_to_phys, then passes dev_addr to
> > is_xen_swiotlb_buffer that calls xen_bus_to_phys again.
>
> It does?
>
> I see it call mfn_to_local_pfn which calls pfn_to_mfn and
> get_phys_to_machine
On Thu, Oct 17, 2013 at 06:43:33PM +0100, Stefano Stabellini wrote:
> xen_unmap_single calls xen_bus_to_phys, then passes dev_addr to
> is_xen_swiotlb_buffer that calls xen_bus_to_phys again.
It does?
I see it call mfn_to_local_pfn which calls pfn_to_mfn and
get_phys_to_machine (which I presume
On Thu, Oct 17, 2013 at 06:43:33PM +0100, Stefano Stabellini wrote:
xen_unmap_single calls xen_bus_to_phys, then passes dev_addr to
is_xen_swiotlb_buffer that calls xen_bus_to_phys again.
It does?
I see it call mfn_to_local_pfn which calls pfn_to_mfn and
get_phys_to_machine (which I presume is
On Thu, Oct 17, 2013 at 06:43:33PM +0100, Stefano Stabellini wrote:
xen_unmap_single calls xen_bus_to_phys, then passes dev_addr to
is_xen_swiotlb_buffer that calls xen_bus_to_phys again.
It does?
I see it call mfn_to_local_pfn which calls pfn_to_mfn and
get_phys_to_machine (which I
On Wed, Oct 23, 2013 at 06:34:13PM +0100, Stefano Stabellini wrote:
On Thu, Oct 17, 2013 at 06:43:33PM +0100, Stefano Stabellini wrote:
xen_unmap_single calls xen_bus_to_phys, then passes dev_addr to
is_xen_swiotlb_buffer that calls xen_bus_to_phys again.
It does?
I see it call
xen_unmap_single calls xen_bus_to_phys, then passes dev_addr to
is_xen_swiotlb_buffer that calls xen_bus_to_phys again.
xen_bus_to_phys is potentially a slow operation that might involve
walking a tree.
We can avoid calling xen_bus_to_phys twice by removing the
is_xen_swiotlb_buffer call and doing
xen_unmap_single calls xen_bus_to_phys, then passes dev_addr to
is_xen_swiotlb_buffer that calls xen_bus_to_phys again.
xen_bus_to_phys is potentially a slow operation that might involve
walking a tree.
We can avoid calling xen_bus_to_phys twice by removing the
is_xen_swiotlb_buffer call and doing
10 matches
Mail list logo