From: Greg KH <gregkh@linuxfoundation.org>
To: Jay Wang <wanjay@amazon.com>
Cc: stable@vger.kernel.org, David Woodhouse <dwmw@amazon.co.uk>,
Thomas Gleixner <tglx@linutronix.de>,
Michael Kelley <mhkelley@outlook.com>
Subject: Re: [PATCH v5.10/v5.15/v6.1] x86/i8253: Disable PIT timer 0 when not in use
Date: Wed, 19 Feb 2025 06:55:49 +0100 [thread overview]
Message-ID: <2025021959-headfirst-dayroom-c1bc@gregkh> (raw)
In-Reply-To: <20250218203526.17408-1-wanjay@amazon.com>
On Tue, Feb 18, 2025 at 08:35:23PM +0000, Jay Wang wrote:
> commit 70e6b7d9ae3c63df90a7bba7700e8d5c300c3c60 upstream
>
> Leaving the PIT interrupt running can cause noticeable steal time for
> virtual guests. The VMM generally has a timer which toggles the IRQ input
> to the PIC and I/O APIC, which takes CPU time away from the guest. Even
> on real hardware, running the counter may use power needlessly (albeit
> not much).
>
> Make sure it's turned off if it isn't going to be used.
>
> Signed-off-by: David Woodhouse <dwmw@amazon.co.uk>
> Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
> Tested-by: Michael Kelley <mhkelley@outlook.com>
> Link: https://lore.kernel.org/all/20240802135555.564941-1-dwmw2@infradead.org
> Signed-off-by: Jay Wang <wanjay@amazon.com>
> Cc: stable@vger.kernel.org #v5.10/v5.15/v6.1
> ---
> arch/x86/kernel/i8253.c | 11 +++++++++--
> drivers/clocksource/i8253.c | 13 +++++++++----
> include/linux/i8253.h | 1 +
> 3 files changed, 19 insertions(+), 6 deletions(-)
Why don't you also want this in 6.6.y? You can't submit patches for
only older kernels without them also being in newer ones, otherwise you
will get a regression when upgrading.
Please always submit patches for all relevant kernel trees.
thanks,
greg k-h
next prev parent reply other threads:[~2025-02-19 5:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-18 20:35 [PATCH v5.10/v5.15/v6.1] x86/i8253: Disable PIT timer 0 when not in use Jay Wang
2025-02-19 5:55 ` Greg KH [this message]
2025-02-20 9:32 ` [PATCH v1 v5.10/v5.15/v6.1/v6.6] Please also incorporate this patch into 6.6.y Jay Wang
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=2025021959-headfirst-dayroom-c1bc@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=dwmw@amazon.co.uk \
--cc=mhkelley@outlook.com \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=wanjay@amazon.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.