linux-kernel - Re: [ANNOUNCE / RFC] PUCK Future Topics

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: <864jglbgsh.wl-maz@kernel.org>
Date:   Thu, 14 Dec 2023 03:32:14 +0000
From:   Marc Zyngier <maz@...nel.org>
To:     Sean Christopherson <seanjc@...gle.com>
Cc:     kvm@...r.kernel.org, linux-kernel@...r.kernel.org,
        Paolo Bonzini <pbonzini@...hat.com>,
        James Houghton <jthoughton@...gle.com>,
        Peter Xu <peterx@...hat.com>,
        Axel Rasmussen <axelrasmussen@...gle.com>,
        Oliver Upton <oliver.upton@...ux.dev>,
        Isaku Yamahata <isaku.yamahata@...ux.intel.com>,
        David Matlack <dmatlack@...gle.com>,
        Yan Zhao <yan.y.zhao@...el.com>,
        Michael Roth <michael.roth@....com>,
        Aaron Lewis <aaronlewis@...gle.com>
Subject: Re: [ANNOUNCE / RFC] PUCK Future Topics

On Thu, 14 Dec 2023 00:17:53 +0000,
Sean Christopherson <seanjc@...gle.com> 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.