|
|
|
|
|
|
|
|
|
|
xen-devel
Re: [Xen-devel] Question regarding SLAB corruption
> Oh! I take it then that the infiniband driver will call sync_single() on
> subsections of a mapped region? I haven't seen that behaviour before and it
> will kill lib/swiotlb.c (the generic Linux swiotlb implementation) just as
> surely as it does the Xen-specific swiotlb!
> We could make the swiotlb robust to this treatment, I guess. It will involve
> initialising all covered io_tlb_orig_addr[] slots rather than just the
> first.
Does this mean that lib/swiotlb.c's swiotlb_sync_single_range_for_cpu()
and swiotlb_sync_single_range_for_device() are broken? Given that (as
you say) io_tlb_orig_addr[] only gets one slot filled in at the end of
map_single(), I don't see any way it could work if more than one page
is mapped.
- R.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- Re: [Xen-devel] Question regarding SLAB corruption, (continued)
- Re: [Xen-devel] Question regarding SLAB corruption, Roland Dreier
- Re: [Xen-devel] Question regarding SLAB corruption, Lukas Hejtmanek
- Re: [Xen-devel] Question regarding SLAB corruption, Roland Dreier
- Re: [Xen-devel] Question regarding SLAB corruption, Lukas Hejtmanek
- Re: [Xen-devel] Question regarding SLAB corruption, Keir Fraser
- Re: [Xen-devel] Question regarding SLAB corruption, Keir Fraser
- [Xen-devel] Question: Dynamic code in x86_64 Xen, Santos, Jose Renato G
- [Xen-devel] Re: Question: Dynamic code in x86_64 Xen, Keir Fraser
- [Xen-devel] RE: Question: Dynamic code in x86_64 Xen, Santos, Jose Renato G
- Re: [Xen-devel] Question regarding SLAB corruption, Roland Dreier
- Re: [Xen-devel] Question regarding SLAB corruption,
Roland Dreier <=
- Re: [Xen-devel] Question regarding SLAB corruption, Keir Fraser
- [Xen-devel] Question regarding vm creat&boot, tgh
- Re: [Xen-devel] Question regarding SLAB corruption, Roland Dreier
|
|
|
|
|