From: Dave Hansen <dave.hansen@intel.com>
To: David Rientjes <rientjes@google.com>,
Alexander Graf <graf@amazon.com>,
Anthony Yznaga <anthony.yznaga@oracle.com>,
David Hildenbrand <david@redhat.com>,
Frank van der Linden <fvdl@google.com>,
James Gowans <jgowans@amazon.com>,
Jason Gunthorpe <jgg@nvidia.com>,
Junaid Shahid <junaids@google.com>,
Mike Rapoport <rppt@kernel.org>,
Pankaj Gupta <pankaj.gupta.linux@gmail.com>,
Pasha Tatashin <tatashin@google.com>,
Pratyush Yadav <pratyush@kernel.org>,
Vipin Sharma <vipinsh@google.com>,
Vishal Annapurve <vannapurve@google.com>,
"Woodhouse, David" <dwmw@amazon.co.uk>
Cc: linux-mm@kvack.org, kexec@lists.infradead.org
Subject: Re: [Hypervisor Live Update] Notes from April 21, 2025
Date: Mon, 28 Apr 2025 17:35:07 -0700 [thread overview]
Message-ID: <087a7b3b-a2d4-4596-af53-d0f850ea6aa2@intel.com> (raw)
In-Reply-To: <e03d2bdb-29b2-a0ba-1b7f-1f924dc47285@google.com>
On 4/27/25 23:20, David Rientjes wrote:
> KHO v6 is now staged in Andrew's mm-new tree. We discussed what it will
> take for this series to be pushed to Linus, specifically around
> Reviewed-by tags. There is not a ton of x86 specific code, but it would
> likely be useful to have Reviewed-bys from some x86 maintainers. Dave
> Hansen, would you be the right person to take a look at this from an x86
> perspective?
It looks mostly OK.
The one worry is the scratch reservation sizing, how folks will get that
right, and the implications if they get it wrong. If it's undersized
because newer kernels need more space, what ends up happening? Is it
just an OOM during boot?
next prev parent reply other threads:[~2025-04-29 0:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-28 6:20 David Rientjes
2025-04-29 0:35 ` Dave Hansen [this message]
2025-04-29 8:00 ` Mike Rapoport
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=087a7b3b-a2d4-4596-af53-d0f850ea6aa2@intel.com \
--to=dave.hansen@intel.com \
--cc=anthony.yznaga@oracle.com \
--cc=david@redhat.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=pankaj.gupta.linux@gmail.com \
--cc=pratyush@kernel.org \
--cc=rientjes@google.com \
--cc=rppt@kernel.org \
--cc=tatashin@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