From: "Thomas Hellström (Intel)" <thomas_os@shipmail.org>
To: Zack Rusin <zackr@vmware.com>, linux-kernel@vger.kernel.org
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-mm@kvack.org
Subject: Re: [PATCH] mm/mapping_dirty_helpers: Guard hugepage pud's usage
Date: Fri, 9 Apr 2021 09:43:32 +0200 [thread overview]
Message-ID: <0a742aa1-572f-a62f-677f-af430d47a19c@shipmail.org> (raw)
In-Reply-To: <20210408191529.677958-1-zackr@vmware.com>
On 4/8/21 9:15 PM, Zack Rusin wrote:
> Lets make sure we don't use pud hugepage helpers on architectures
> which do not support it. This fixes the code on arm64.
nits:
Perhaps be a little more specific about what it fixes? I figure it's a
compilation failure?
Also please use imperative form: "Fix the code arm64" rather than "This
fixes the code on arm64"
Other than that LGTM.
Reviewed-by: Thomas Hellström (Intel) <thomas_os@shipmail.org>
>
> Signed-off-by: Zack Rusin <zackr@vmware.com>
> Cc: Andrew Morton <akpm@linux-foundation.org>
> Cc: Thomas Hellström (Intel) <thomas_os@shipmail.org>
> Cc: linux-mm@kvack.org
> Cc: linux-kernel@vger.kernel.org
> ---
> mm/mapping_dirty_helpers.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/mm/mapping_dirty_helpers.c b/mm/mapping_dirty_helpers.c
> index b59054ef2e10..b890854ec761 100644
> --- a/mm/mapping_dirty_helpers.c
> +++ b/mm/mapping_dirty_helpers.c
> @@ -165,10 +165,12 @@ static int wp_clean_pud_entry(pud_t *pud, unsigned long addr, unsigned long end,
> return 0;
> }
>
> +#ifdef CONFIG_HAVE_ARCH_TRANSPARENT_HUGEPAGE_PUD
> /* Huge pud */
> walk->action = ACTION_CONTINUE;
> if (pud_trans_huge(pudval) || pud_devmap(pudval))
> WARN_ON(pud_write(pudval) || pud_dirty(pudval));
> +#endif
>
> return 0;
> }
prev parent reply other threads:[~2021-04-09 7:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-08 19:15 [PATCH] mm/mapping_dirty_helpers: Guard hugepage pud's usage Zack Rusin
2021-04-09 7:43 ` Thomas Hellström (Intel) [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=0a742aa1-572f-a62f-677f-af430d47a19c@shipmail.org \
--to=thomas_os@shipmail.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=zackr@vmware.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;
as well as URLs for NNTP newsgroup(s).