From: Sean Christopherson <seanjc@google.com>
To: Chao Peng <chao.p.peng@linux.intel.com>
Cc: kvm@vger.kernel.org, Paolo Bonzini <pbonzini@redhat.com>,
Sagi Shahar <sagis@google.com>,
Erdem Aktas <erdemaktas@google.com>,
Anish Ghulati <aghulati@google.com>,
Oliver Upton <oliver.upton@linux.dev>,
James Houghton <jthoughton@google.com>,
Anish Moorthy <amoorthy@google.com>,
Ben Gardon <bgardon@google.com>,
David Matlack <dmatlack@google.com>,
Ricardo Koller <ricarkol@google.com>,
Axel Rasmussen <axelrasmussen@google.com>,
Aaron Lewis <aaronlewis@google.com>,
Ashish Kalra <ashish.kalra@amd.com>,
Babu Moger <babu.moger@amd.com>, Chao Gao <chao.gao@intel.com>,
Chenyi Qiang <chenyi.qiang@intel.com>,
David Woodhouse <dwmw@amazon.co.uk>,
Emanuele Giuseppe Esposito <eesposit@redhat.com>,
Gavin Shan <gshan@redhat.com>, Guang Zeng <guang.zeng@intel.com>,
Hou Wenlong <houwenlong.hwl@antgroup.com>,
Jiaxi Chen <jiaxi.chen@linux.intel.com>,
Jim Mattson <jmattson@google.com>, Jing Liu <jing2.liu@intel.com>,
Junaid Shahid <junaids@google.com>,
Kai Huang <kai.huang@intel.com>,
Leonardo Bras <leobras@redhat.com>,
Like Xu <like.xu.linux@gmail.com>,
Li RongQing <lirongqing@baidu.com>,
"Maciej S . Szmigiero" <maciej.szmigiero@oracle.com>,
Maxim Levitsky <mlevitsk@redhat.com>,
Michael Roth <michael.roth@amd.com>, Michal Luczaj <mhal@rbox.co>,
Mingwei Zhang <mizhang@google.com>,
Nikunj A Dadhania <nikunj@amd.com>,
Paul Durrant <pdurrant@amazon.com>,
Peng Hao <flyingpenghao@gmail.com>,
Peter Gonda <pgonda@google.com>, Peter Xu <peterx@redhat.com>,
Robert Hoo <robert.hu@linux.intel.com>,
Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>,
Tom Lendacky <thomas.lendacky@amd.com>,
Vipin Sharma <vipinsh@google.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
Wanpeng Li <wanpengli@tencent.com>,
Wei Wang <wei.w.wang@intel.com>,
Xiaoyao Li <xiaoyao.li@intel.com>,
Yu Zhang <yu.c.zhang@linux.intel.com>,
Will Deacon <will@kernel.org>, Marc Zyngier <maz@kernel.org>,
David Hildenbrand <david@redhat.com>,
Fuad Tabba <tabba@google.com>,
Isaku Yamahata <isaku.yamahata@gmail.com>,
Qinglan Xiang <qinglan.xiang@intel.com>,
Kai Svahn <kai.svahn@intel.com>,
Margarita Maroto <margarita.maroto@intel.com>,
Anil Keshavamurthy <anil.s.keshavamurthy@intel.com>,
Nagareddy Reddy <nspreddy@google.com>,
linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE / RFC] Periodic Upstream Call for KVM
Date: Tue, 23 May 2023 00:07:15 +0000 [thread overview]
Message-ID: <ZGwDs1qHcl8PX+m2@google.com> (raw)
In-Reply-To: <20230522072508.GA326851@chaop.bj.intel.com>
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.
next prev parent reply other threads:[~2023-05-23 0:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-12 23:10 [ANNOUNCE / RFC] Periodic Upstream Call for KVM Sean Christopherson
2023-05-18 19:50 ` Michael Roth
2023-05-22 7:25 ` Chao Peng
2023-05-23 0:07 ` Sean Christopherson [this message]
2023-05-23 2:19 ` Chao Peng
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZGwDs1qHcl8PX+m2@google.com \
--to=seanjc@google.com \
--cc=aaronlewis@google.com \
--cc=aghulati@google.com \
--cc=amoorthy@google.com \
--cc=anil.s.keshavamurthy@intel.com \
--cc=ashish.kalra@amd.com \
--cc=axelrasmussen@google.com \
--cc=babu.moger@amd.com \
--cc=bgardon@google.com \
--cc=chao.gao@intel.com \
--cc=chao.p.peng@linux.intel.com \
--cc=chenyi.qiang@intel.com \
--cc=david@redhat.com \
--cc=dmatlack@google.com \
--cc=dwmw@amazon.co.uk \
--cc=eesposit@redhat.com \
--cc=erdemaktas@google.com \
--cc=flyingpenghao@gmail.com \
--cc=gshan@redhat.com \
--cc=guang.zeng@intel.com \
--cc=houwenlong.hwl@antgroup.com \
--cc=isaku.yamahata@gmail.com \
--cc=jiaxi.chen@linux.intel.com \
--cc=jing2.liu@intel.com \
--cc=jmattson@google.com \
--cc=jthoughton@google.com \
--cc=junaids@google.com \
--cc=kai.huang@intel.com \
--cc=kai.svahn@intel.com \
--cc=kvm@vger.kernel.org \
--cc=leobras@redhat.com \
--cc=like.xu.linux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lirongqing@baidu.com \
--cc=maciej.szmigiero@oracle.com \
--cc=margarita.maroto@intel.com \
--cc=maz@kernel.org \
--cc=mhal@rbox.co \
--cc=michael.roth@amd.com \
--cc=mizhang@google.com \
--cc=mlevitsk@redhat.com \
--cc=nikunj@amd.com \
--cc=nspreddy@google.com \
--cc=oliver.upton@linux.dev \
--cc=pbonzini@redhat.com \
--cc=pdurrant@amazon.com \
--cc=peterx@redhat.com \
--cc=pgonda@google.com \
--cc=qinglan.xiang@intel.com \
--cc=ricarkol@google.com \
--cc=robert.hu@linux.intel.com \
--cc=sagis@google.com \
--cc=suravee.suthikulpanit@amd.com \
--cc=tabba@google.com \
--cc=thomas.lendacky@amd.com \
--cc=vipinsh@google.com \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.com \
--cc=wei.w.wang@intel.com \
--cc=will@kernel.org \
--cc=xiaoyao.li@intel.com \
--cc=yu.c.zhang@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox