linux-kernel - Re: [PATCH vhost next 09/10] vdpa/mlx5: Add shared memory registration code

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: <ad3c6157-2224-8e1f-7afb-deb9b45f568e@redhat.com>
Date:   Thu, 16 Jul 2020 17:32:38 +0800
From:   Jason Wang <jasowang@...hat.com>
To:     Eli Cohen <eli@...lanox.com>
Cc:     mst@...hat.com, virtualization@...ts.linux-foundation.org,
        linux-kernel@...r.kernel.org, shahafs@...lanox.com,
        saeedm@...lanox.com, Parav Pandit <parav@...lanox.com>
Subject: Re: [PATCH vhost next 09/10] vdpa/mlx5: Add shared memory
 registration code


On 2020/7/16 下午4:28, Eli Cohen wrote:
> On Thu, Jul 16, 2020 at 04:13:21PM +0800, Jason Wang wrote:
>> On 2020/7/16 下午3:23, Eli Cohen wrote:
>>> Add code to support registering guest's memory region for the device.
>>
>> It would be better to use "userspace" memory here since vhost-vDPA
>> could be used by e.g dpdk application on the host in the future.
>>
> How about replaciing "guest's memory" with "address space". It is more
> general and aligns with the with the fact that virio driver can run in
> the guest's kernel.


Probably but note that guest driver is not the only user for this. It 
could be either:

1) Guest virtio driver
2) Userspace virtio driver on the host
3) Kernel virtio driver on the host.

Thanks


>