Kexec Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Pratyush Yadav <pratyush@kernel.org>
To: Pasha Tatashin <pasha.tatashin@soleen.com>,
	Mike Rapoport <rppt@kernel.org>, Alexander Graf <graf@amazon.com>,
	Sean Christopherson <seanjc@google.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Jason Gunthorpe <jgg@nvidia.com>,
	David Woodhouse <dwmw2@infradead.org>,
	Logan Odell <loganodell@google.com>,
	David Matlack <dmatlack@google.com>,
	Samiullah Khawaja <skhawaja@google.com>,
	Tarun Sahu <tarunsahu@google.com>,
	Sourabh Jain <sourabhjain@linux.ibm.com>,
	Pranjal Shrivastava <praan@google.com>,
	Vipin Sharma <vipinsh@google.com>
Cc: kexec@lists.infradead.org, Pratyush Yadav <pratyush@kernel.org>
Subject: [ANNOUNCE] Live Update BoF at LPC 2026
Date: Thu, 01 Oct 2026 21:47:50 +0200	[thread overview]
Message-ID: <2vxzh5j5kxsp.fsf@kernel.org> (raw)

Hi all,

The proposal for a Live Update BoF has been accepted. The BoF is
scheduled on Monday October 5th at 12:00. Event link:
https://lpc.events/event/20/contributions/2641/

The primary topic of discussion will be LUO/KHO ABI and what type of
backwards and forwards compatibility should be guaranteed for the ABI.
There are different opinions from various parts of the community and
this would be a chance to bring out all views and come to an agreement.
More context can be found at these mailing list threads: [0][1].

Other list of potential topics, time permitting:

- TMPFS preservation [2][3].
- Getting rid of scratch/bootmem areas.
- KHO enablement on different architectures like Loongarch or PowerPC.
- Making KHO work with crash reservations and KASAN.

This list is open to suggestions.

Hope to see you there!

[0] https://lore.kernel.org/kexec/2vxzik5f311e.fsf@kernel.org/#r
[1] https://lore.kernel.org/kexec/20260904160009.GV4157646@nvidia.com/#r
[2] https://lore.kernel.org/kexec/20260923224408.3745689-1-pratyush@kernel.org/T/#u
[3] https://lore.kernel.org/kexec/20260901180713.4185641-1-dmatlack@google.com/T/#u

-- 
Regards,
Pratyush Yadav


             reply	other threads:[~2026-10-01 19:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-01 19:47 Pratyush Yadav [this message]
2026-10-01 20:10 ` [ANNOUNCE] Live Update BoF at LPC 2026 David Woodhouse
2026-10-01 22:59   ` Pasha Tatashin

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=2vxzh5j5kxsp.fsf@kernel.org \
    --to=pratyush@kernel.org \
    --cc=dmatlack@google.com \
    --cc=dwmw2@infradead.org \
    --cc=graf@amazon.com \
    --cc=jgg@nvidia.com \
    --cc=kexec@lists.infradead.org \
    --cc=loganodell@google.com \
    --cc=pasha.tatashin@soleen.com \
    --cc=pbonzini@redhat.com \
    --cc=praan@google.com \
    --cc=rppt@kernel.org \
    --cc=seanjc@google.com \
    --cc=skhawaja@google.com \
    --cc=sourabhjain@linux.ibm.com \
    --cc=tarunsahu@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