Received-SPF: pass (google.com: domain of linux-kernel+bounces-128740-linux.lists.archive=gmail.com@vger.kernel.org designates 139.178.88.99 as permitted sender) client-ip=139.178.88.99;
Date: Tue, 2 Apr 2024 14:42:12 -0700
In-Reply-To: <DS0PR11MB6373543451F0505C220F2C8ADC382@DS0PR11MB6373.namprd11.prod.outlook.com>
Precedence: bulk
Mime-Version: 1.0
References: <20240313003211.1900117-1-seanjc@google.com> <DS0PR11MB6373543451F0505C220F2C8ADC382@DS0PR11MB6373.namprd11.prod.outlook.com>
Message-ID: <Zgx7tA9c8RYv3hVa@google.com>
Subject: Re: [ANNOUNCE] PUCK Agenda - 2024.03.13 - No topic
From: Sean Christopherson <seanjc@google.com>
To: Wei W Wang <wei.w.wang@intel.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>, 
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, David Skidmore <davidskidmore@google.com>, 
	Steve Rutherford <srutherford@google.com>, Pankaj Gupta <pankaj.gupta@amd.com>, 
	Paolo Bonzini <pbonzini@redhat.com>
Content-Type: text/plain; charset="us-ascii"

On Sun, Mar 31, 2024, Wei W Wang wrote:
> On Wednesday, March 13, 2024 8:32 AM, Sean Christopherson wrote:
> > To: Sean Christopherson <seanjc@google.com>
> > Cc: kvm@vger.kernel.org; linux-kernel@vger.kernel.org
> > Subject: [ANNOUNCE] PUCK Agenda - 2024.03.13 - No topic
> > 
> > No topic for tomorrow, but I'll be online.
> > 
> > Note, the US just did its Daylight Savings thing, so the local time might be
> > different for you this week.
> > 
> > Note #2, PUCK is canceled for the next two weeks as I'll be offline.
> > 
> > Future Schedule:
> > March    20th - CANCELED
> > March    27th - CANCELED
> 
> Would there be a slot available on April 3rd?
> I'd like to have a discussion about KVM uAPIs for TDX and SNP Live Migration.
> 
> CC the ones who would be interested in joining the discussion.
> (Hope more folks working on the SNP migration part could join)

What exactly do you want to discuss and/or achieve?  We can have a handwavy
discussion about TDX's needs for live migration, but there's basically zero chance
you'll get concrete feedback on exact uAPIs at this stage (we haven't even nailed
down the core TDX and SNP uAPI).  Doubly so without first giving people *something*
to look at.  Even a very rough RFC would go a long way toward showing/describing
the problem you need/want to solve.