Linux-mm Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Pasha Tatashin <pasha.tatashin@soleen.com>
To: David Matlack <dmatlack@google.com>
Cc: Pasha Tatashin <pasha.tatashin@soleen.com>,
	 Alexander Graf <graf@amazon.com>,
	"Andersen, Tycho" <Tycho.Andersen@amd.com>,
	 Anthony Yznaga <anthony.yznaga@oracle.com>,
	Baolu Lu <baolu.lu@linux.intel.com>,
	 David Hildenbrand <david@kernel.org>,
	"Heyne, Maximillian" <mheyne@amazon.de>,
	 James Gowans <jgowans@amazon.com>,
	Jason Gunthorpe <jgg@nvidia.com>,
	 Mike Rapoport <rppt@kernel.org>,
	Pankaj Gupta <pankaj.gupta.linux@gmail.com>,
	 Pratyush Yadav <pratyush@kernel.org>,
	Praveen Kumar <kpraveen.lkml@gmail.com>,
	 Vipin Sharma <vipinsh@google.com>,
	Vishal Annapurve <vannapurve@google.com>,
	 "Woodhouse, David" <dwmw@amazon.co.uk>,
	Luca Boccassi <luca.boccassi@gmail.com>,
	 Samiullah Khawaja <skhawaja@google.com>,
	Jork Loeser <jloeser@linux.microsoft.com>,
	linux-mm@kvack.org,  kexec@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [Hypervisor Live Update] Notes from May 18, 2026
Date: Wed, 27 May 2026 14:41:37 +0000	[thread overview]
Message-ID: <ahcCXlbbnsxUAfeb@plex> (raw)
In-Reply-To: <CALzav=dkVWYmbWCO6wDuQrxetAcqYkitJiRF_BhDDGqn2_-RKA@mail.gmail.com>

On 05-26 11:53, David Matlack wrote:
> On Tue, May 26, 2026 at 11:37 AM Pasha Tatashin
> <pasha.tatashin@soleen.com> wrote:
> 
> > Next meeting will be on Monday, June 1 at 8am PDT (UTC-7), everybody is
> > welcome: https://meet.google.com/rjn-dmzu-hgq
> >
> > Topics for the next meeting:
> > - Vipin and David Matlack roadmap for PCI and VFIO changes to solicit
> >   upstream feedback
> 
> Hey Pasha,
> 
> We'll need to push this back by one meeting (June 15th) due to the US
> holiday and some out-of-office leave we didn't account for.

Understood. We will address this on June 15th.

Thank you,
Pasha

> 
> > - Status of I/O freezing implementations and HugeTLB fallback allocation
> >   patches
> > - PCI core changes v6 review and next steps
> > - IOMMU persistence v3 and roadmap progress
> > - Updates on vm_splice investigations for CRIU memory preservation
> > - later: KHO support for Confidential VMs including page table
> >   preservation and pinning
> > - later: versioning support for luo to negotiate
> > - later: KHO enlightenment for ASI
> > - later: testing methodology to allow downstream consumers to qualify
> >   that live update works from one version to another
> > - later: reducing blackout window during live update


      reply	other threads:[~2026-05-27 14:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-26 18:37 [Hypervisor Live Update] Notes from May 18, 2026 Pasha Tatashin
2026-05-26 18:53 ` David Matlack
2026-05-27 14:41   ` Pasha Tatashin [this message]

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=ahcCXlbbnsxUAfeb@plex \
    --to=pasha.tatashin@soleen.com \
    --cc=Tycho.Andersen@amd.com \
    --cc=anthony.yznaga@oracle.com \
    --cc=baolu.lu@linux.intel.com \
    --cc=david@kernel.org \
    --cc=dmatlack@google.com \
    --cc=dwmw@amazon.co.uk \
    --cc=graf@amazon.com \
    --cc=jgg@nvidia.com \
    --cc=jgowans@amazon.com \
    --cc=jloeser@linux.microsoft.com \
    --cc=kexec@lists.infradead.org \
    --cc=kpraveen.lkml@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=luca.boccassi@gmail.com \
    --cc=mheyne@amazon.de \
    --cc=pankaj.gupta.linux@gmail.com \
    --cc=pratyush@kernel.org \
    --cc=rppt@kernel.org \
    --cc=skhawaja@google.com \
    --cc=vannapurve@google.com \
    --cc=vipinsh@google.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