Re: [tip: sched/core] x86/tsc: Always save/restore TSC sched_clock() on suspend/resume
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: [tip: sched/core] x86/tsc: Always save/restore TSC sched_clock() on suspend/resume
- From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
- Date: Fri, 21 Feb 2025 20:17:13 +0100
- Cc: linux-tip-commits@xxxxxxxxxxxxxxx, "Guilherme G. Piccoli" <gpiccoli@xxxxxxxxxx>, Ingo Molnar <mingo@xxxxxxxxxx>, stable@xxxxxxxxxxxxxxx, Thomas Gleixner <tglx@xxxxxxxxxxxxx>, Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>, x86@xxxxxxxxxx
- In-reply-to: <174014866289.10177.10974658062988825500.tip-bot2@tip-bot2>
- References: <20250215210314.351480-1-gpiccoli@igalia.com> <174014866289.10177.10974658062988825500.tip-bot2@tip-bot2>
On Fri, Feb 21, 2025 at 02:37:42PM -0000, tip-bot2 for Guilherme G. Piccoli wrote:
> The following commit has been merged into the sched/core branch of tip:
>
> Commit-ID: d90c9de9de2f1712df56de6e4f7d6982d358cabe
> Gitweb: https://git.kernel.org/tip/d90c9de9de2f1712df56de6e4f7d6982d358cabe
> Author: Guilherme G. Piccoli <gpiccoli@xxxxxxxxxx>
> AuthorDate: Sat, 15 Feb 2025 17:58:16 -03:00
> Committer: Ingo Molnar <mingo@xxxxxxxxxx>
> CommitterDate: Fri, 21 Feb 2025 15:27:38 +01:00
>
> x86/tsc: Always save/restore TSC sched_clock() on suspend/resume
Should this not go into x86/core or somesuch?
[Index of Archives]
[Linux Stable Commits]
[Linux Stable Kernel]
[Linux Kernel]
[Linux USB Devel]
[Linux Video &Media]
[Linux Audio Users]
[Yosemite News]
[Linux SCSI]