[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a60cb31b7181a685c38ebfc8d7c721609c8dce0b@linux.dev>
Date: Thu, 09 Nov 2023 15:47:48 +0000
From: jeff.xie@...ux.dev
To: "Matthew Wilcox" <willy@...radead.org>
Cc: akpm@...ux-foundation.org, iamjoonsoo.kim@....com, vbabka@...e.cz,
cl@...ux.com, penberg@...nel.org, rientjes@...gle.com,
roman.gushchin@...ux.dev, 42.hyeyoo@...il.com, linux-mm@...ck.org,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
chensong_2000@....cn, xiehuan09@...il.com
Subject: Re: [RFC][PATCH 4/4] mm/rmap: implement anonmap allocate post
callback for page_owner
November 9, 2023 at 10:10 PM, "Matthew Wilcox" <willy@...radead.org> wrote:
>
> On Thu, Nov 09, 2023 at 11:25:21AM +0800, Jeff Xie wrote:
>
> >
> > +static int anon_alloc_post_page_owner(struct folio *folio, struct task_struct *tsk,
> > + void *data, char *kbuf, size_t count)
> > +{
> > + int ret;
> > + unsigned long address = (unsigned long)data;
> > +
> > + ret = scnprintf(kbuf, count, "ANON_PAGE address 0x%lx\n", address);
> >
>
> ... completely ignoring that it might have been mremap() since ...
>
> I'm not an expert on anon memory. I'm sure someone can tell you how to
> figure out the current address that a folio is mapped at.
>
I'm currently not sure if the address parameter is the mapped address, so this is an RFC patchset ;-)
__
Jeff Xie
Powered by blists - more mailing lists