From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 1F846C7EE2A for ; Tue, 23 May 2023 00:39:46 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234922AbjEWAjo (ORCPT ); Mon, 22 May 2023 20:39:44 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39970 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235629AbjEWAXE (ORCPT ); Mon, 22 May 2023 20:23:04 -0400 Received: from mail-pg1-x54a.google.com (mail-pg1-x54a.google.com [IPv6:2607:f8b0:4864:20::54a]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 6DBFB212E for ; Mon, 22 May 2023 17:07:17 -0700 (PDT) Received: by mail-pg1-x54a.google.com with SMTP id 41be03b00d2f7-53488b6a929so2219256a12.0 for ; Mon, 22 May 2023 17:07:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20221208; t=1684800437; x=1687392437; h=cc:to:from:subject:message-id:references:mime-version:in-reply-to :date:from:to:cc:subject:date:message-id:reply-to; bh=00M59/ERL5rCid+0EeexM90p8FMZ55e8xTVk/5IwWAI=; b=eKS08NvvMxcTks/gD/Aef3buBTIRd89+5ZUYMh1veW2Bwau8N4vvj1C9yASUIO/Gl1 oxHyQwzG9vN+C/niZsJ++pGG2eokuUJnWPCjy6ek3v5mPoLqVq8whstRJFwEID2GUHec Mi9oBdwFZDPfV7XB9rTviIM16S5fpiSaIMHo3VNaob6ESktjrnlVgQMzSw721XDdv87x 1GZq2rhXbQfTFYPhNp99bfZY1T5TXRdPui6I+y0hdirdTSX84g6S5Kb1osAfq+3Sd+c/ XgTs77NQ8/gz2esL3Leed4EPQBrJE0uEuWzjOpKjOrBYvCEl9OYgP2+Uk05chf+qs3j7 baXA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1684800437; x=1687392437; h=cc:to:from:subject:message-id:references:mime-version:in-reply-to :date:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=00M59/ERL5rCid+0EeexM90p8FMZ55e8xTVk/5IwWAI=; b=kpS44BXnGCTMH+RD3RBEsWrLPQLxsQdEBAnJ3QcAMO9iKbFFcSrF/V3/a9XjIJajgq fpw+uzi+Ljek7uI49YyvzWD2qMX0C371D2ZivDFBNwTZ9fVi4bvKn2/dTNrrrQrXOF3M +ZuGbcd1kVNuAw9wl88mZD63npnF5lmV/J0LETWEgCLgA5jFKLx7Yc4fCfLReGizUvzY Iro4lXuV/Wd9yBoO9Tmrkf5hI7mQEjRuvVBDgfTy5bKlTGSizGwhrKCJUW6Zi4RzuxMl GWcjZRT8PwKm4aNZGzliyisOBkJTi0EK9ooa3MAlwekFl6yDyRmiTZFZfEryuliQuZSe /fng== X-Gm-Message-State: AC+VfDw97IX8iVzMHGlTQve/3X+47At0zRukws3dBfyT9m5jASlaxNMt S4kJKr2JBZLL20V88Yu9PPK1Kz1r9jA= X-Google-Smtp-Source: ACHHUZ4h8CKM4xTy1lkpuF74m6v7QXKl/pIuViq4YXbsPdpBl9vkZ+vUKUQxs/EZ3XZmIxBRr/AUmQ9wf74= X-Received: from zagreus.c.googlers.com ([fda3:e722:ac3:cc00:7f:e700:c0a8:5c37]) (user=seanjc job=sendgmr) by 2002:a63:ba08:0:b0:534:9003:d58e with SMTP id k8-20020a63ba08000000b005349003d58emr2722120pgf.9.1684800436821; Mon, 22 May 2023 17:07:16 -0700 (PDT) Date: Tue, 23 May 2023 00:07:15 +0000 In-Reply-To: <20230522072508.GA326851@chaop.bj.intel.com> Mime-Version: 1.0 References: <20230512231026.799267-1-seanjc@google.com> <20230522072508.GA326851@chaop.bj.intel.com> Message-ID: Subject: Re: [ANNOUNCE / RFC] Periodic Upstream Call for KVM From: Sean Christopherson To: Chao Peng Cc: kvm@vger.kernel.org, Paolo Bonzini , Sagi Shahar , Erdem Aktas , Anish Ghulati , Oliver Upton , James Houghton , Anish Moorthy , Ben Gardon , David Matlack , Ricardo Koller , Axel Rasmussen , Aaron Lewis , Ashish Kalra , Babu Moger , Chao Gao , Chenyi Qiang , David Woodhouse , Emanuele Giuseppe Esposito , Gavin Shan , Guang Zeng , Hou Wenlong , Jiaxi Chen , Jim Mattson , Jing Liu , Junaid Shahid , Kai Huang , Leonardo Bras , Like Xu , Li RongQing , "Maciej S . Szmigiero" , Maxim Levitsky , Michael Roth , Michal Luczaj , Mingwei Zhang , Nikunj A Dadhania , Paul Durrant , Peng Hao , Peter Gonda , Peter Xu , Robert Hoo , Suravee Suthikulpanit , Tom Lendacky , Vipin Sharma , Vitaly Kuznetsov , Wanpeng Li , Wei Wang , Xiaoyao Li , Yu Zhang , Will Deacon , Marc Zyngier , David Hildenbrand , Fuad Tabba , Isaku Yamahata , Qinglan Xiang , Kai Svahn , Margarita Maroto , Anil Keshavamurthy , Nagareddy Reddy , linux-kernel@vger.kernel.org Content-Type: text/plain; charset="us-ascii" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, May 22, 2023, Chao Peng wrote: > On Fri, May 12, 2023 at 04:10:27PM -0700, Sean Christopherson wrote: > > PT (6am) > > MT (7am) > > CT (8am) > > ET (9am) > > WET (2pm) > > CET (3pm) > > EET (4pm) > > EST (5pm) > > CST (9pm) > > NZST (1am) > > This looks good, 9pm is not too late for PRC people. > > > > > The obvious alternative would be to invert the schedule and have the sync be in > > the evening/night for Pacific Time, but to get 6am for ARM folks, we end up with: > > > > PT (10pm) > > MT (11pm) > > CT (12pm) > > ET (1am) > > WET (6am) > > CET (7am) > > EET (8am) > > EST (9am) > > CST (1pm) > > NZST (5pm) > > > > which is quite unreasonable for pretty much everyone based in the US. Earlier > > than 6am for WET is likewise unreasonable and will result in people not attending. > > 9pm for China is also unreasonable, but I hope that it's not completely ridiculous > > and is doable enough that people can at least attend on an as-needed basis. Sorry > > Kai, as the sole representative from New Zealand, you get hosed :-( > > > > Wednesday because holidays and (short) vacations most often land at the beginning > > and end of the week. > > > > 60 minutes because I'm not waking up at dawn for anything less, and anything > > more will likely have dimishing returns, especially for folks on the edges of > > the time zone table. > > > > Lastly, the big unknown is which video communication software to use. My default > > is obviously Google Meet, but I've been told that Meet is unusable in some > > countries. :-/ My only requirements (beyond basic, obvious functionality) are > > that (a) there's a web interface (no install required) and that (b) the calls can > > be recorded. > > Google Meet should work for me, but may not for every (PRC) people. > Besides no installation, if no registration would be even better ;) > Maybe we can run with Google Meet for the first session(s) if you > havn't get one in your mind, it's not too hard to switch to alternative > at a later time right? Ya, switching should be no problem. Let's try Google Meet and go from there. Thanks much for the input! > > To kick things off, I am leaning toward a "launch" date of May 24th (Pacific), > > with KVM guest private mem (a.k.a. UPM) as the first topic. > > Thanks for driving this, yes for UPM I would definitely join. I'm going to push out the inagaural date one week until May 31st, partly to give more time for this to get widely disseminated, but mostly because I need to write down my various thoughts on where to go with UPM, and I don't think I'll get that done before Wednesday. That'll also give me time to setup a public calendar so that people can get reminders and whatnot.