Re: [PATCH 3/3] mm: unexport follow_pfn

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

To: Jason Gunthorpe <jgg@xxxxxxxxxx>, Daniel Vetter <daniel.vetter@xxxxxxxx>
Subject: Re: [PATCH 3/3] mm: unexport follow_pfn
From: Paolo Bonzini <pbonzini@xxxxxxxxxx>
Date: Wed, 24 Mar 2021 15:31:04 +0100
Cc: DRI Development <dri-devel@xxxxxxxxxxxxxxxxxxxxx>, LKML <linux-kernel@xxxxxxxxxxxxxxx>, kvm@xxxxxxxxxxxxxxx, linux-mm@xxxxxxxxx, linux-arm-kernel@xxxxxxxxxxxxxxxxxxx, linux-samsung-soc@xxxxxxxxxxxxxxx, linux-media@xxxxxxxxxxxxxxx, 3pvd@xxxxxxxxxx, Jann Horn <jannh@xxxxxxxxxx>, Cornelia Huck <cohuck@xxxxxxxxxx>, Peter Xu <peterx@xxxxxxxxxx>, Alex Williamson <alex.williamson@xxxxxxxxxx>, Daniel Vetter <daniel.vetter@xxxxxxxxx>
In-reply-to: <20210324125211.GA2356281@nvidia.com>
References: <20210316153303.3216674-1-daniel.vetter@ffwll.ch> <20210316153303.3216674-4-daniel.vetter@ffwll.ch> <20210324125211.GA2356281@nvidia.com>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.7.0

On 24/03/21 13:52, Jason Gunthorpe wrote:

I think this is the right thing to do.

Alex is working on fixing VFIO and while kvm is still racy using
follow pte, I think they are working on it too?


Yeah, or at least we have a plan.

Paolo

References:
- [PATCH 0/3] switch to unsafe_follow_pfn
  - From: Daniel Vetter
- [PATCH 3/3] mm: unexport follow_pfn
  - From: Daniel Vetter
- Re: [PATCH 3/3] mm: unexport follow_pfn
  - From: Jason Gunthorpe

Prev by Date: Re: [PATCH v5 1/5] mm,memory_hotplug: Allocate memmap from the added memory range
Next by Date: Re: [PATCH v5 1/5] mm,memory_hotplug: Allocate memmap from the added memory range
Previous by thread: Re: [PATCH 3/3] mm: unexport follow_pfn
Next by thread: Re: [PATCH 3/3] mm: unexport follow_pfn
Index(es):
- Date
- Thread

[Index of Archives] [Linux ARM Kernel] [Linux ARM] [Linux Omap] [Fedora ARM] [IETF Annouce] [Bugtraq] [Linux OMAP] [Linux MIPS] [eCos] [Asterisk Internet PBX] [Linux API]