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-next>] [day] [month] [year] [list]
Date:   Mon, 1 Feb 2021 19:44:24 -0400
From:   Jason Gunthorpe <>
To:     "Tian, Kevin" <>
Cc:     "Song Bao Hua (Barry Song)" <>,
        "chensihang (A)" <>,
        Arnd Bergmann <>,
        Greg Kroah-Hartman <>,
        "" <>,
        "" <>,
        "" <>,
        Zhangfei Gao <>,
        "Liguozhu (Kenneth)" <>,
Subject: Re: [RFC PATCH v2] uacce: Add uacce_ctrl misc device

On Fri, Jan 29, 2021 at 10:09:03AM +0000, Tian, Kevin wrote:
> > SVA is not doom to work with IO page fault only. If we have SVA+pin,
> > we would get both sharing address and stable I/O latency.
> Isn't it like a traditional MAP_DMA API (imply pinning) plus specifying 
> cpu_va of the memory pool as the iova? 

I think their issue is the HW can't do the cpu_va trick without also
involving the system IOMMU in a SVA mode

It really is something that belongs under some general /dev/sva as we
talked on the vfio thread


Powered by blists - more mailing lists