From: Peter Xu <peterx@redhat.com>
To: "Huang, Ying" <ying.huang@intel.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Andrea Arcangeli <aarcange@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
"Kirill A . Shutemov" <kirill@shutemov.name>,
Nadav Amit <nadav.amit@gmail.com>,
Hugh Dickins <hughd@google.com>,
David Hildenbrand <david@redhat.com>,
Vlastimil Babka <vbabka@suse.cz>,
Andi Kleen <andi.kleen@intel.com>
Subject: Re: [PATCH RFC 0/4] mm: Remember young bit for migration entries
Date: Mon, 1 Aug 2022 18:25:40 -0400 [thread overview]
Message-ID: <YuhS5DcwwNvy2Rkn@xz-m1.local> (raw)
In-Reply-To: <87pmhkjzo7.fsf@yhuang6-desk2.ccr.corp.intel.com>
On Mon, Aug 01, 2022 at 01:33:28PM +0800, Huang, Ying wrote:
> If my understanding were correct, max_swapfile_size() provides a
> mechanism to identify the available bits with swp_entry_t and swap PTE
> considered. We may take advantage of that?
That's an interesting trick, I'll have a closer look, thanks for the
pointer!
>
> And according to commit 377eeaa8e11f ("x86/speculation/l1tf: Limit swap
> file size to MAX_PA/2"), the highest bit of swap offset needs to be 0 if
> L1TF mitigation is enabled.
>
> Cced Andi for confirmation.
Yeah it'll be great to have a confirmation, hopefully max_swapfile_size()
should have covered that case.
--
Peter Xu
next prev parent reply other threads:[~2022-08-01 22:25 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-29 1:40 Peter Xu
2022-07-29 1:40 ` [PATCH RFC 1/4] mm/swap: Add swp_offset_pfn() to fetch PFN from swap entry Peter Xu
2022-08-01 3:13 ` Huang, Ying
2022-08-01 22:29 ` Peter Xu
2022-08-02 1:22 ` Huang, Ying
2022-07-29 1:40 ` [PATCH RFC 2/4] mm: Remember young bit for page migrations Peter Xu
2022-07-29 1:40 ` [PATCH RFC 3/4] mm/x86: Use SWP_TYPE_BITS in 3-level swap macros Peter Xu
2022-07-29 1:40 ` [PATCH RFC 4/4] mm/x86: Define __ARCH_SWP_OFFSET_BITS Peter Xu
2022-07-29 17:07 ` [PATCH RFC 0/4] mm: Remember young bit for migration entries Nadav Amit
2022-07-29 22:43 ` Peter Xu
2022-08-01 3:20 ` Huang, Ying
2022-08-01 5:33 ` Huang, Ying
2022-08-01 22:25 ` Peter Xu [this message]
2022-08-01 8:21 ` David Hildenbrand
2022-08-01 22:35 ` Peter Xu
2022-08-02 12:06 ` David Hildenbrand
2022-08-02 20:14 ` Peter Xu
2022-08-02 20:23 ` David Hildenbrand
2022-08-02 20:35 ` Peter Xu
2022-08-02 20:59 ` David Hildenbrand
2022-08-02 22:15 ` Peter Xu
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=YuhS5DcwwNvy2Rkn@xz-m1.local \
--to=peterx@redhat.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=andi.kleen@intel.com \
--cc=david@redhat.com \
--cc=hughd@google.com \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nadav.amit@gmail.com \
--cc=vbabka@suse.cz \
--cc=ying.huang@intel.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