From: David Rientjes <rientjes@google.com>
To: James Gowans <jgowans@amazon.com>,
Dave Hansen <dave.hansen@intel.com>,
Matthew Wilcox <willy@infradead.org>,
Pasha Tatashin <tatashin@google.com>,
Alexander Graf <graf@amazon.com>,
David Woodhouse <dwmw@amazon.co.uk>,
Jason Gunthorpe <jgg@nvidia.com>,
Frank van der Linden <fvdl@google.com>,
Vipin Sharma <vipinsh@google.com>,
David Matlack <dmatlack@google.com>,
Junaid Shahid <junaids@google.com>,
Vishal Annapurve <vannapurve@google.com>
Cc: David Hildenbrand <david@redhat.com>,
Mike Rapoport <rppt@kernel.org>,
Pratyush Yadav <pratyush@kernel.org>,
linux-mm@kvack.org, kexec@lists.infradead.org
Subject: [Feedback Needed] Hypervisor live update biweekly meeting time
Date: Sun, 12 Jan 2025 22:45:01 -0800 (PST) [thread overview]
Message-ID: <2908e4ab-abc4-ddd0-b191-fe820856cfb4@google.com> (raw)
Hi all,
Following up from discussions at the end of last year on two topics from
the Linux MM Alignment Sessions, memory persistence across kexec[1] and
Kexec Hand-Off (KHO)[2], we'd like to start up a biweekly series dedicated
to this topic to accelerate alignment and progress.
We discussed this in-session as a mechanism to accelerate discussion on
pertinent topics as well as get regular status updates on progress. This
obviously does *not* replace upstream discussion on the mailing list, but
is rather meant to accelerate it. Regular summaries for each session will
continue to be posted on linux-mm and kexec mailing lists.
Per the attendees on the Cc list, the ideal time is likely biweekly on
Mondays at 8:00-9:00am PST (UTC-8). Since next Monday is a holiday in the
United States, we'd start Monday, January 27 (this will also avoid the
holiday in February).
I'm planning on inviting everybody on the To and Cc lists of this email.
If you are also interested in attending, please email me *privately* so I
can add you to the invite and shared drive. If you are listed and are not
interested in attending, same thing :)
If this time does *NOT* work for you, please also email me privately so we
can try to develop another slot. Given the number of people involved, and
how geographically distributed we are, our mileage may vary. The time of
day, 8am PST, is basically etched into stone given this is the most
convenient time for the people on the Cc list :)
Thank you!
Time zones
PST (UTC-8) 8:00am
MST (UTC-7) 9:00am
CST (UTC-6) 10:00am
EST (UTC-5) 11:00am
Rio de Janeiro (UTC-3) 1:00pm
London (UTC) 4:00pm
Berlin (UTC+1) 5:00pm
Moscow (UTC+3) 7:00pm
Dubai (UTC+4) 8:00pm
Mumbai (UTC+5:30) 9:30pm
Singapore (UTC+8) 12:00am Tuesday
Beijing (UTC+8) 12:00am Tuesday
Tokyo (UTC+9) 1:00am Tuesday
Sydney (UTC+11) 3:00am Tuesday
Auckland (UTC+13) 5:00am Tuesday
[1]
https://lore.kernel.org/linux-mm/CAPTztWZ26YQmtDbXowUzrRUSb2mmbQksztHfbRYYTgDm9Gc_og@mail.gmail.com/T/
[2]
https://lore.kernel.org/linux-mm/52e189fa-bbb4-f031-8a64-716ddee14599@google.com/T/
next reply other threads:[~2025-01-13 6:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-13 6:45 David Rientjes [this message]
2025-01-20 20:20 ` David Rientjes
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=2908e4ab-abc4-ddd0-b191-fe820856cfb4@google.com \
--to=rientjes@google.com \
--cc=dave.hansen@intel.com \
--cc=david@redhat.com \
--cc=dmatlack@google.com \
--cc=dwmw@amazon.co.uk \
--cc=fvdl@google.com \
--cc=graf@amazon.com \
--cc=jgg@nvidia.com \
--cc=jgowans@amazon.com \
--cc=junaids@google.com \
--cc=kexec@lists.infradead.org \
--cc=linux-mm@kvack.org \
--cc=pratyush@kernel.org \
--cc=rppt@kernel.org \
--cc=tatashin@google.com \
--cc=vannapurve@google.com \
--cc=vipinsh@google.com \
--cc=willy@infradead.org \
/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