Re: [PATCH RFC 04/12] kernel/user: Allow user::locked_vm to be usable for iommufd

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: [PATCH RFC 04/12] kernel/user: Allow user::locked_vm to be usable for iommufd
From: Jason Gunthorpe <jgg@xxxxxxxxxx>
Date: Tue, 29 Mar 2022 08:46:11 -0300
Cc: "Tian, Kevin" <kevin.tian@xxxxxxxxx>, Alex Williamson <alex.williamson@xxxxxxxxxx>, Niklas Schnelle <schnelle@xxxxxxxxxxxxx>, Lu Baolu <baolu.lu@xxxxxxxxxxxxxxx>, Chaitanya Kulkarni <chaitanyak@xxxxxxxxxx>, Cornelia Huck <cohuck@xxxxxxxxxx>, Daniel Jordan <daniel.m.jordan@xxxxxxxxxx>, David Gibson <david@xxxxxxxxxxxxxxxxxxxxx>, Eric Auger <eric.auger@xxxxxxxxxx>, "iommu@xxxxxxxxxxxxxxxxxxxxxxxxxx" <iommu@xxxxxxxxxxxxxxxxxxxxxxxxxx>, Jean-Philippe Brucker <jean-philippe@xxxxxxxxxx>, "Martins, Joao" <joao.m.martins@xxxxxxxxxx>, "kvm@xxxxxxxxxxxxxxx" <kvm@xxxxxxxxxxxxxxx>, Matthew Rosato <mjrosato@xxxxxxxxxxxxx>, "Michael S. Tsirkin" <mst@xxxxxxxxxx>, Nicolin Chen <nicolinc@xxxxxxxxxx>, Shameerali Kolothum Thodi <shameerali.kolothum.thodi@xxxxxxxxxx>, "Liu, Yi L" <yi.l.liu@xxxxxxxxx>, Keqian Zhu <zhukeqian1@xxxxxxxxxx>, Sean Mooney <smooney@xxxxxxxxxx>
In-reply-to: <CACGkMEu_Zc+xBR0G9qNR6XQKNY9MLfTvbpgzpL2kNC4ri3DRQg@mail.gmail.com>
References: <BN9PR11MB5276BED72D82280C0A4C6F0C8C199@BN9PR11MB5276.namprd11.prod.outlook.com> <CACGkMEutpbOc_+5n3SDuNDyHn19jSH4ukSM9i0SUgWmXDydxnA@mail.gmail.com> <BN9PR11MB5276E3566D633CEE245004D08C199@BN9PR11MB5276.namprd11.prod.outlook.com> <CACGkMEvTmCFqAsc4z=2OXOdr7X--0BSDpH06kCiAP5MHBjaZtg@mail.gmail.com> <BN9PR11MB5276ECF1F1C7D0A80DA086D18C199@BN9PR11MB5276.namprd11.prod.outlook.com> <CACGkMEtpWemw6tj=suxNjvSHuixyzhMJBYmqdbhQkinuWNADCQ@mail.gmail.com> <20220324114605.GX11336@nvidia.com> <CACGkMEtTVMuc-JebEbTrb3vRUVaNJ28FV_VyFRdRquVQN9VeQA@mail.gmail.com> <20220328122239.GL1342626@nvidia.com> <CACGkMEu_Zc+xBR0G9qNR6XQKNY9MLfTvbpgzpL2kNC4ri3DRQg@mail.gmail.com>

On Tue, Mar 29, 2022 at 12:59:52PM +0800, Jason Wang wrote:

> vDPA has a backend feature negotiation, then actually, userspace can
> tell vDPA to go with the new accounting approach. Not sure RDMA can do
> the same.

A security feature userspace can ask to turn off is not really a
security feature.

Jason

References:
- RE: [PATCH RFC 04/12] kernel/user: Allow user::locked_vm to be usable for iommufd
  - From: Tian, Kevin
- Re: [PATCH RFC 04/12] kernel/user: Allow user::locked_vm to be usable for iommufd
  - From: Jason Wang
- RE: [PATCH RFC 04/12] kernel/user: Allow user::locked_vm to be usable for iommufd
  - From: Tian, Kevin
- Re: [PATCH RFC 04/12] kernel/user: Allow user::locked_vm to be usable for iommufd
  - From: Jason Wang
- RE: [PATCH RFC 04/12] kernel/user: Allow user::locked_vm to be usable for iommufd
  - From: Tian, Kevin
- Re: [PATCH RFC 04/12] kernel/user: Allow user::locked_vm to be usable for iommufd
  - From: Jason Wang
- Re: [PATCH RFC 04/12] kernel/user: Allow user::locked_vm to be usable for iommufd
  - From: Jason Gunthorpe
- Re: [PATCH RFC 04/12] kernel/user: Allow user::locked_vm to be usable for iommufd
  - From: Jason Wang
- Re: [PATCH RFC 04/12] kernel/user: Allow user::locked_vm to be usable for iommufd
  - From: Jason Gunthorpe
- Re: [PATCH RFC 04/12] kernel/user: Allow user::locked_vm to be usable for iommufd
  - From: Jason Wang

Prev by Date: Re: [PATCH 2/2] s390x: add test for SIGP STORE_ADTL_STATUS order
Next by Date: Re: [PATCH 3/3] KVM: arm64: Start trapping ID registers for 32 bit guests
Previous by thread: Re: [PATCH RFC 04/12] kernel/user: Allow user::locked_vm to be usable for iommufd
Next by thread: Re: [PATCH RFC 04/12] kernel/user: Allow user::locked_vm to be usable for iommufd
Index(es):
- Date
- Thread

[Index of Archives] [KVM ARM] [KVM ia64] [KVM ppc] [Virtualization Tools] [Spice Development] [Libvirt] [Libvirt Users] [Linux USB Devel] [Linux Audio Users] [Yosemite Questions] [Linux Kernel] [Linux SCSI] [XFree86]