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]
Date:   Fri, 3 May 2019 05:29:02 -0700
From:   Christoph Hellwig <>
To:     Maxim Levitsky <>
Cc:, Fam Zheng <>,
        Keith Busch <>,
        Sagi Grimberg <>,,
        "David S . Miller" <>,
        Greg Kroah-Hartman <>,
        Liang Cunming <>,
        Wolfram Sang <>,,
        Kirti Wankhede <>,
        Jens Axboe <>,
        Alex Williamson <>,
        John Ferlan <>,
        Mauro Carvalho Chehab <>,
        Paolo Bonzini <>,
        Liu Changpeng <>,
        "Paul E . McKenney " <>,
        Amnon Ilan <>, Christoph Hellwig <>,
        Nicolas Ferre <>,
        Jens Axboe <>
Subject: Re: [PATCH v2 06/10] nvme/core: add mdev interfaces

On Thu, May 02, 2019 at 02:47:57PM +0300, Maxim Levitsky wrote:
> If the mdev device driver also sets the
> NVME_F_MDEV_DMA_SUPPORTED, the mdev core will
> dma map all the guest memory into the nvme device,
> so that nvme device driver can use dma addresses as passed
> from the mdev core driver

We really need a proper block layer interface for that so that
uring or the nvme target can use pre-mapping as well.

Powered by blists - more mailing lists