From: Peter Zijlstra <peterz@infradead.org>
To: Atharva Tiwari <evepolonium@gmail.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
Valentin Schneider <vschneid@redhat.com>,
Lakshmi Sowjanya D <lakshmi.sowjanya.d@intel.com>,
Peter Hilber <peter.hilber@opensynergy.com>,
"Christopher S. Hall" <christopher.s.hall@intel.com>,
Feng Tang <feng.tang@intel.com>,
Randy Dunlap <rdunlap@infradead.org>,
Marco Elver <elver@google.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86 tsc: avoid system instability in hibernation
Date: Tue, 10 Dec 2024 13:35:16 +0100 [thread overview]
Message-ID: <20241210123516.GP8562@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <20241210062446.2413-1-evepolonium@gmail.com>
On Tue, Dec 10, 2024 at 11:54:18AM +0530, Atharva Tiwari wrote:
> System instability are seen during resume from hibernation when system
> is under heavy CPU load. This is due to the lack of update of sched
> clock data, and the scheduler would then think that heavy CPU hog
> tasks need more time in CPU, causing the system to freeze
> during the unfreezing of tasks.
Please tell me more.. what crazy things are happening?
next prev parent reply other threads:[~2024-12-10 12:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-10 6:24 [PATCH] x86 tsc: avoid system instability in hibernation Atharva Tiwari
2024-12-10 12:35 ` Peter Zijlstra [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-12-10 13:39 Atharva Tiwari
2024-12-17 13:51 ` kernel test robot
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=20241210123516.GP8562@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bp@alien8.de \
--cc=bsegall@google.com \
--cc=christopher.s.hall@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=dietmar.eggemann@arm.com \
--cc=elver@google.com \
--cc=evepolonium@gmail.com \
--cc=feng.tang@intel.com \
--cc=hpa@zytor.com \
--cc=juri.lelli@redhat.com \
--cc=lakshmi.sowjanya.d@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peter.hilber@opensynergy.com \
--cc=rdunlap@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
--cc=x86@kernel.org \
/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