From: SeongJae Park <sj@kernel.org>
To: akpm@linux-foundation.org
Cc: oleksandr@natalenko.name, john.stultz@linaro.org,
tglx@linutronix.de, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, SeongJae Park <sj@kernel.org>
Subject: [PATCH v3 0/2] mm/damon: Fix fake /proc/loadavg reports
Date: Fri, 26 Nov 2021 14:50:13 +0000 [thread overview]
Message-ID: <20211126145015.15862-1-sj@kernel.org> (raw)
This patchset fixes DAMON's fake load report issue. The first patch
makes yet another variant of usleep_range() for this fix, and the second
patch fixes the issue of DAMON by making it using the newly introduced
function.
I think these need to be applied on v5.15.y, but the second patch cannot
cleanly applied there as is. I will back-port this on v5.15.y and post
later once this is merged in the mainline. If you think this is not
appropriate for stable tree, please let me know.
Changelog
---------
From v2
(https://lore.kernel.org/linux-mm/20211125160830.30153-1-sj@kernel.org/)
- Cc Oleksandr (Oleksandr Natalenko)
- Add 'Suggested-by:' for Andrew Morton on the first patch
From v1
(https://lore.kernel.org/linux-mm/20211124145219.32866-1-sj@kernel.org/)
- Avoid copy-and-pasting usleep_delay() in DAMON code (Andrew Morton)
SeongJae Park (2):
timers: Implement usleep_idle_range()
mm/damon/core: Fix fake load reports due to uninterruptible sleeps
include/linux/delay.h | 14 +++++++++++++-
kernel/time/timer.c | 16 +++++++++-------
mm/damon/core.c | 6 +++---
3 files changed, 25 insertions(+), 11 deletions(-)
--
2.17.1
next reply other threads:[~2021-11-26 14:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-26 14:50 SeongJae Park [this message]
2021-11-26 14:50 ` [PATCH v3 1/2] timers: Implement usleep_idle_range() SeongJae Park
2021-11-26 21:26 ` Thomas Gleixner
2021-11-26 14:50 ` [PATCH v3 2/2] mm/damon/core: Fix fake load reports due to uninterruptible sleeps SeongJae Park
2021-11-27 13:09 ` [PATCH v3 0/2] mm/damon: Fix fake /proc/loadavg reports Oleksandr Natalenko
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=20211126145015.15862-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=oleksandr@natalenko.name \
--cc=tglx@linutronix.de \
/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).