linux-kernel - Re: [PATCH v1] device-dax: Adding match parameter to select which driver to match dax devices

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 for Android: free password hash cracker in your pocket

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

Date:   Wed, 23 Mar 2022 10:44:28 +0800
From:   Zhenguo Yao <yaozhenguo1@...il.com>
To:     Dan Williams <dan.j.williams@...el.com>
Cc:     Vishal L Verma <vishal.l.verma@...el.com>,
        Dave Jiang <dave.jiang@...el.com>,
        Linux NVDIMM <nvdimm@...ts.linux.dev>,
        姚振国 <yaozhenguo@...com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v1] device-dax: Adding match parameter to select which
 driver to match dax devices

I thought about it carefully. Indeed, in my scenario(virtual machine which use
optane as DRAM), device assignment can be performed in userspace at very
early time after the system is started. This patch is not needed in my
scenario. Thank you for your reply.

Dan Williams <dan.j.williams@...el.com> 于2022年3月23日周三 10:01写道：
>
> On Mon, Feb 28, 2022 at 1:50 AM Zhenguo Yao <yaozhenguo1@...il.com> wrote:
> >
> > device_dax driver always match dax devices by default. The other
> > drivers only match devices by dax_id. There are situations which
> > need kmem drvier match all the dax device at boot time. So
> > adding a parameter to support this function.
>
> What are the situations that happen at boot time that can't wait for
> initramfs or userspace to move the device assignment?