Re: [RFC PATCH 15/19] kvm: handle KVM_EXIT_MEMORY_FAULT

2023-08-09 Thread Xu Yilun
On 2023-07-31 at 12:21:57 -0400, Xiaoyao Li wrote: > From: Chao Peng > > Currently only KVM_MEMORY_EXIT_FLAG_PRIVATE in flags is valid when > KVM_EXIT_MEMORY_FAULT happens. It indicates userspace needs to do > the memory conversion on the RAMBlock to turn the memory into desired > attribute, i.e.

Re: [RFC PATCH 0/6] Enable shared device assignment

2024-07-31 Thread Xu Yilun
On Fri, Jul 26, 2024 at 09:08:51AM +0200, David Hildenbrand wrote: > On 26.07.24 07:02, Tian, Kevin wrote: > > > From: David Hildenbrand > > > Sent: Thursday, July 25, 2024 10:04 PM > > > > > > > Open > > > > > > > > Implementing a RamDiscardManager to notify VFIO of page conversions > > > >

Re: [PATCH 2/7] guest_memfd: Introduce an object to manage the guest-memfd with RamDiscardManager

2025-02-06 Thread Xu Yilun
On Thu, Jan 30, 2025 at 11:28:11AM -0500, Peter Xu wrote: > On Sun, Jan 26, 2025 at 11:34:29AM +0800, Xu Yilun wrote: > > > Definitely not suggesting to install an invalid pointer anywhere. The > > > mapped pointer will still be valid for gmem for example, but the fault >

Re: [PATCH 2/7] guest_memfd: Introduce an object to manage the guest-memfd with RamDiscardManager

2025-01-10 Thread Xu Yilun
> > > > https://github.com/aik/qemu/commit/3663f889883d4aebbeb0e4422f7be5e357e2ee46 > > > > but I am not sure if this ever saw the light of the day, did not it? > > (ironically I am using it as a base for encrypted DMA :) ) > > Yeah, we are doing the same work. I saw a solution from Michael long

Re: [PATCH 2/7] guest_memfd: Introduce an object to manage the guest-memfd with RamDiscardManager

2025-01-10 Thread Xu Yilun
On Fri, Jan 10, 2025 at 05:00:22AM +0800, Xu Yilun wrote: > > > > > > https://github.com/aik/qemu/commit/3663f889883d4aebbeb0e4422f7be5e357e2ee46 > > > > > > but I am not sure if this ever saw the light of the day, did not it? > > > (ironica

Re: [PATCH 2/7] guest_memfd: Introduce an object to manage the guest-memfd with RamDiscardManager

2025-01-20 Thread Xu Yilun
On Mon, Jan 20, 2025 at 03:46:15PM -0500, Peter Xu wrote: > On Mon, Jan 20, 2025 at 09:22:50PM +1100, Alexey Kardashevskiy wrote: > > > It is still uncertain how to implement the private MMIO. Our assumption > > > is the private MMIO would also create a memory region with > > > guest_memfd-like bac

Re: [PATCH 2/7] guest_memfd: Introduce an object to manage the guest-memfd with RamDiscardManager

2025-01-22 Thread Xu Yilun
On Wed, Jan 22, 2025 at 03:30:05PM +1100, Alexey Kardashevskiy wrote: > > > On 22/1/25 02:18, Peter Xu wrote: > > On Tue, Jun 25, 2024 at 12:31:13AM +0800, Xu Yilun wrote: > > > On Mon, Jan 20, 2025 at 03:46:15PM -0500, Peter Xu wrote: > > > > On Mon, Jan

Re: [PATCH 2/7] guest_memfd: Introduce an object to manage the guest-memfd with RamDiscardManager

2025-01-23 Thread Xu Yilun
On Wed, Jan 22, 2025 at 11:43:01AM -0500, Peter Xu wrote: > On Wed, Jan 22, 2025 at 05:41:31PM +0800, Xu Yilun wrote: > > On Wed, Jan 22, 2025 at 03:30:05PM +1100, Alexey Kardashevskiy wrote: > > > > > > > > > On 22/1/25 02:18, Peter Xu wrote: > > > &

Re: [PATCH 2/7] guest_memfd: Introduce an object to manage the guest-memfd with RamDiscardManager

2025-01-24 Thread Xu Yilun
On Thu, Jan 23, 2025 at 11:47:17AM -0500, Peter Xu wrote: > On Thu, Jan 23, 2025 at 05:33:53PM +0800, Xu Yilun wrote: > > On Wed, Jan 22, 2025 at 11:43:01AM -0500, Peter Xu wrote: > > > On Wed, Jan 22, 2025 at 05:41:31PM +0800, Xu Yilun wrote: > > > > On Wed, Ja

Re: [PATCH 2/7] guest_memfd: Introduce an object to manage the guest-memfd with RamDiscardManager

2025-01-25 Thread Xu Yilun
> Definitely not suggesting to install an invalid pointer anywhere. The > mapped pointer will still be valid for gmem for example, but the fault > isn't. We need to differenciate two things (1) virtual address mapping, > then (2) permission and accesses on the folios / pages of the mapping. > Her

Re: [PATCH 2/7] guest_memfd: Introduce an object to manage the guest-memfd with RamDiscardManager

2025-01-13 Thread Xu Yilun
On Mon, Jan 13, 2025 at 11:34:44AM +0800, Chenyi Qiang wrote: > > > On 1/10/2025 5:50 AM, Xu Yilun wrote: > > On Fri, Jan 10, 2025 at 05:00:22AM +0800, Xu Yilun wrote: > >>>> > >>>> https://github.com/aik/qemu/commit/3663f889883d4aebbeb0e4422f7be5