Re: [ANNOUNCE / RFC] PUCK Future Topics

[Marc Zyngier]

On Thu, 14 Dec 2023 00:17:53 +0000,
Sean Christopherson <seanjc@xxxxxxxxxx> wrote:
> 
> Hi all!  There are a handful of PUCK topics that I want to get scheduled, and
> would like your help/input in confirming attendance to ensure we reach critical
> mass.
> 
> If you are on the Cc, please confirm that you are willing and able to attend
> PUCK on the proposed/tentative date for any topics tagged with your name.  Or
> if you simply don't want to attend, I suppose that's a valid answer too. :-)
> 
> If you are not on the Cc but want to ensure that you can be present for a given
> topic, please speak up asap if you have a conflict.  I will do my best to
> accomodate everyone's schedules, and the more warning I get the easier that will
> be.
> 
> Note, the proposed schedule is largely arbitrary, I am not wedded to any
> particular order.  The only known conflict at this time is the guest_memfd()
> post-copy discussion can't land on Jan 10th.
> 
> Thanks!
> 
> 
> 2024.01.03 - Post-copy for guest_memfd()
>     Needs: David M, Paolo, Peter Xu, James, Oliver, Aaron
> 
> 2024.01.10 - Unified uAPI for protected VMs
>     Needs: Paolo, Isaku, Mike R
> 
> 2024.01.17 - Memtypes for non-coherent MDA

DMA?

>     Needs: Paolo, Yan, Oliver, Marc, more ARM folks?

Do we need anyone from the other architectures? I wouldn't be
surprised if RISC-V was at least as picky as ARM on that front
(assuming this really is about DMA and not something else).

	M.

-- 
Without deviation from the norm, progress is not possible.