linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Pratyush Yadav <pratyush@kernel.org>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: Pratyush Yadav <pratyush@kernel.org>,
	 David Rientjes <rientjes@google.com>,
	 Alexander Graf <graf@amazon.com>,
	 Anthony Yznaga <anthony.yznaga@oracle.com>,
	 Dave Hansen <dave.hansen@intel.com>,
	 David Hildenbrand <david@redhat.com>,
	 Frank van der Linden <fvdl@google.com>,
	James Gowans <jgowans@amazon.com>,
	 Junaid Shahid <junaids@google.com>,
	Matthew Wilcox <willy@infradead.org>,
	 Mike Rapoport <rppt@kernel.org>,
	Pankaj Gupta <pankaj.gupta.linux@gmail.com>,
	 Pasha Tatashin <tatashin@google.com>,
	 Vipin Sharma <vipinsh@google.com>,
	 Vishal Annapurve <vannapurve@google.com>,
	 "Woodhouse, David" <dwmw@amazon.co.uk>,
	 linux-mm@kvack.org,  kexec@lists.infradead.org
Subject: Re: [Hypervisor Live Update] Notes from March 10, 2025
Date: Wed, 26 Mar 2025 16:18:29 +0000	[thread overview]
Message-ID: <mafs0a597sr3e.fsf@kernel.org> (raw)
In-Reply-To: <20250320122303.GT9311@nvidia.com>

On Thu, Mar 20 2025, Jason Gunthorpe wrote:

>> I didn't mean the exact flags value, but the ability to have
>> per-folio flags. The exact bits and their meaning would of course
>> need to be part of the ABI. Shmem uses the dirty and uptodate flags
>> to track some state on the folios, and the flags can affect it's
>> behavior (lazily zeroing out falloc-ed pages for example). I am
>> assuming other FD types or drivers might also want to store
>> per-folio information. Having KHO core provide this facility can
>> avoid duplicating the logic in each subsystem.
>
> For something simple like shmem I'd probably just suggest a side car bitmap
> array or something?
>
> The trouble with trying to feed flags through the xarray thing is that
> the memory holding that pfn data across the kexec is not itself
> preserved memory so it is all blown away once the allocator starts.
>
> Any data that needs to be preserved further has to be copied into the
> frozen struct page, which is pretty limiting in terms of what you
> could preserve. A few bits could maybe work out but not alot of data.

Right, that makes sense. I can live with a sidecar bitmap then.

[...]

-- 
Regards,
Pratyush Yadav


      reply	other threads:[~2025-03-26 16:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-17  3:52 David Rientjes
2025-03-17 17:22 ` Jason Gunthorpe
2025-03-20  5:37   ` Pratyush Yadav
2025-03-20 12:23     ` Jason Gunthorpe
2025-03-26 16:18       ` Pratyush Yadav [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=mafs0a597sr3e.fsf@kernel.org \
    --to=pratyush@kernel.org \
    --cc=anthony.yznaga@oracle.com \
    --cc=dave.hansen@intel.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=rientjes@google.com \
    --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