[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] tg3 NIC driver bug in 3.14.x under Xen [and 3 more messages]
- To: Michael Chan <mchan@xxxxxxxxxxxx>
- From: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
- Date: Thu, 16 Apr 2015 18:15:47 +0100
- Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Sanjeev Bansal <sanjeevb@xxxxxxxxxxxx>, netdev@xxxxxxxxxxxxxxx, Vlad Yasevich <vyasevich@xxxxxxxxx>, Prashant <prashant@xxxxxxxxxxxx>, "Siva Reddy \(Siva\) Kallam" <siva.kallam@xxxxxxxxxxxx>, David Vrabel <david.vrabel@xxxxxxxxxx>, Boris Ostrovsky <boris.ostrovsky@xxxxxxxxxx>, cascardo@xxxxxxxxxxxxxxxxxx
- Delivery-date: Thu, 16 Apr 2015 17:23:00 +0000
- List-id: Xen developer discussion <xen-devel.lists.xen.org>
Michael Chan writes ("Re: tg3 NIC driver bug in 3.14.x under Xen [and 3 more
messages]"):
> On Thu, 2015-04-16 at 09:24 -0300, cascardo@xxxxxxxxxxxxxxxxxx wrote:
> > Yes, this looks like the driver is not syncing the DMA buffers. Unmap is
> > supposed to synchronize as well.
>
> For small rx packets (< 256 bytes), we sync the DMA buffer before we
> copy the data to another SKB. For larger packets, we unmap the DMA
> buffer. Do we see the corruption in both cases?
Yes, at least with swiotlb=force iommu=soft.
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel
|
