From: "Daniel Walker (danielwa)" <danielwa@cisco.com>
To: Anshuman Khandual <anshuman.khandual@arm.com>
Cc: "David Beazley \(dbeazley\)" <dbeazley@cisco.com>,
"Aneesh Kumar K . V" <aneesh.kumar@linux.ibm.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"xe-linux-external\(mailer list\)" <xe-linux-external@cisco.com>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: mm/debug_vm_pgtable.c:860 warning triggered
Date: Mon, 6 Nov 2023 03:22:46 +0000 [thread overview]
Message-ID: <ZUhcBjGZcUQJVHcZ@goliath> (raw)
In-Reply-To: <dc5a1072-0c2b-4f49-8a5f-de3dcfb8c06e@arm.com>
On Mon, Nov 06, 2023 at 08:39:26AM +0530, Anshuman Khandual wrote:
> Hello Daniel,
>
> This test just ensures that PFN is preserved during pte <--> swap pte transformations
> , and the warning here seems to have been caused by powerpc platform specific helpers
> and/or its pte_t representation. Adding powerpc folks and platform mailing list here.
>
> - Anshuman
>
How is the swap support to work if the pte_t is 64bits but the swp_entry_t is 32bits?
I would think there's other platforms which do this.
Daniel
WARNING: multiple messages have this Message-ID (diff)
From: "Daniel Walker (danielwa)" <danielwa@cisco.com>
To: Anshuman Khandual <anshuman.khandual@arm.com>
Cc: Christophe Leroy <christophe.leroy@csgroup.eu>,
"Aneesh Kumar K . V" <aneesh.kumar@linux.ibm.com>,
Michael Ellerman <mpe@ellerman.id.au>,
"David Beazley (dbeazley)" <dbeazley@cisco.com>,
"xe-linux-external(mailer list)" <xe-linux-external@cisco.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: mm/debug_vm_pgtable.c:860 warning triggered
Date: Mon, 6 Nov 2023 03:22:46 +0000 [thread overview]
Message-ID: <ZUhcBjGZcUQJVHcZ@goliath> (raw)
In-Reply-To: <dc5a1072-0c2b-4f49-8a5f-de3dcfb8c06e@arm.com>
On Mon, Nov 06, 2023 at 08:39:26AM +0530, Anshuman Khandual wrote:
> Hello Daniel,
>
> This test just ensures that PFN is preserved during pte <--> swap pte transformations
> , and the warning here seems to have been caused by powerpc platform specific helpers
> and/or its pte_t representation. Adding powerpc folks and platform mailing list here.
>
> - Anshuman
>
How is the swap support to work if the pte_t is 64bits but the swp_entry_t is 32bits?
I would think there's other platforms which do this.
Daniel
next prev parent reply other threads:[~2023-11-06 3:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-03 23:12 mm/debug_vm_pgtable.c:860 warning triggered Daniel Walker (danielwa)
2023-11-06 3:09 ` Anshuman Khandual
2023-11-06 3:09 ` Anshuman Khandual
2023-11-06 3:22 ` Daniel Walker (danielwa) [this message]
2023-11-06 3:22 ` Daniel Walker (danielwa)
2023-11-06 6:06 ` Michael Ellerman
2023-11-06 6:06 ` Michael Ellerman
2023-11-06 9:06 ` David Hildenbrand
2023-11-06 9:06 ` David Hildenbrand
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=ZUhcBjGZcUQJVHcZ@goliath \
--to=danielwa@cisco.com \
--cc=aneesh.kumar@linux.ibm.com \
--cc=anshuman.khandual@arm.com \
--cc=dbeazley@cisco.com \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=xe-linux-external@cisco.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.