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: <20240109002437.GB439767@nvidia.com>
Date: Mon, 8 Jan 2024 20:24:37 -0400
From: Jason Gunthorpe <jgg@...dia.com>
To: Yan Zhao <yan.y.zhao@...el.com>
Cc: Sean Christopherson <seanjc@...gle.com>,
	Oliver Upton <oliver.upton@...ux.dev>, 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>,
	Isaku Yamahata <isaku.yamahata@...ux.intel.com>,
	David Matlack <dmatlack@...gle.com>, Marc Zyngier <maz@...nel.org>,
	Michael Roth <michael.roth@....com>,
	Aaron Lewis <aaronlewis@...gle.com>
Subject: Re: [ANNOUNCE / RFC] PUCK Future Topics

On Mon, Dec 18, 2023 at 01:40:11PM +0800, Yan Zhao wrote:
> +Jason,
> On Fri, Dec 15, 2023 at 12:13:27PM -0800, Sean Christopherson wrote:
> > On Thu, Dec 14, 2023, Oliver Upton wrote:
> > > On Wed, Dec 13, 2023 at 04:17:53PM -0800, Sean Christopherson 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
> > > >     Needs: Paolo, Yan, Oliver, Marc, more ARM folks?
> > > 
> > > Can we move this one? I'm traveling 01.08-01.16 and really don't want
> > > to miss this due to jetlag or travel delays.
> > 
> > Ya, can do.  I'll pencil it in for 01.24.
> > 
> > Yan (and others) would 01.31 work for the "TDP MMU for IOMMU" discussion?  Or if
> > you think you'll be ready earlier, 01.17 is also available (at least for now).
> Either 01.17 or 01.31 is working for me.
> But looks earlier is better :)
> 
> hi Jason,
> Would you like to join the session to discuss "TDP MMU for IOMMU", which is on
> 01.17 or 01.31?
> (6am PDT
>  Video: https://meet.google.com/vdb-aeqo-knk
>  Phone: https://tel.meet/vdb-aeqo-knk?pin=3003112178656
> )

Yes, I can make the 17 it looks like

Thanks,
Jason