linux-kernel - Re: [RFC PATCH 1/3] content: Add VIRTIO_F_SWIOTLB to negotiate use of SWIOTLB bounce buffers

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1fb64766-f945-494c-ba0d-0123cf498ea2@amd.com>
Date: Thu, 3 Apr 2025 15:31:40 +0800
From: Zhu Lingshan <lingshan.zhu@....com>
To: David Woodhouse <dwmw2@...radead.org>, virtio-comment@...ts.linux.dev
Cc: mst@...hat.com, hch@...radead.org, Claire Chang <tientzu@...omium.org>,
 linux-devicetree <devicetree@...r.kernel.org>,
 Rob Herring <robh+dt@...nel.org>, Jörg Roedel
 <joro@...tes.org>, iommu@...ts.linux-foundation.org,
 linux-kernel@...r.kernel.org, graf@...zon.de
Subject: Re: [RFC PATCH 1/3] content: Add VIRTIO_F_SWIOTLB to negotiate use of
 SWIOTLB bounce buffers

On 4/3/2025 3:24 PM, David Woodhouse wrote:
> On Thu, 2025-04-03 at 15:13 +0800, Zhu Lingshan wrote:
>> Hello David
>>
>> IMHO, if we need a bounce buffer, why not place it on the host memory?
> As explained in the cover letter, this is designed for the case where
> the device *cannot* easily access host memory.

Do you mean CoCo encrypted memory? If so, what is the difference between
the host memory side bounce buffer and a device memory bounce buffer
to a guest except the transport(DDR or PCI)? The device should be
able to access host memory side bounce buffer.

Thanks
Zhu Lingshan

>