All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Dave Airlie <airlied@gmail.com>,
	Jani Nikula <jani.nikula@linux.intel.com>,
	Rafael Wysocki <rafael@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	intel-gfx <intel-gfx@lists.freedesktop.org>,
	dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: Linux 6.10-rc1
Date: Mon, 17 Jun 2024 11:27:08 +0200	[thread overview]
Message-ID: <ZnABbKrIzmmEoFEV@duo.ucw.cz> (raw)
In-Reply-To: <CAHk-=wjcdUUip96PnfC+iRjAwPHn3XKsgcohk1ad5VcckCFVKA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1091 bytes --]

Hi!

> > Let's bring in the actual gpu people.. Dave/Jani/others - does any of
> > this sound familiar? Pavel says things have gotten much slower in
> > 6.10: "something was very wrong with the performance, likely to do
> > with graphics"
> 
> Actually, maybe it's not graphics at all. Rafael just sent me a pull
> request that fixes a "turbo is disabled at boot, but magically enabled
> at runtime by firmware" issue.
> 
> The 6.10-rc1 kernel would notice that turbo was disabled, and stopped
> noticing that it magically got re-enabled.
> 
> Pavel, that was with a very different laptop, but who knows... That
> would match the "laptop is much slower" thing.
> 
> So current -git might be worth checking.

So... I went to (then) current -git and I don't want to replace my
machine any more. So the problem should not exist in current mainline.

(I did not have good objective data, so I'm not 100% sure problem was
real in the first place. More like 90% sure.)

Best regards,
								Pavel
-- 
People of Russia, stop Putin before his war on Ukraine escalates.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  parent reply	other threads:[~2024-06-17  9:27 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-26 22:31 Linux 6.10-rc1 Linus Torvalds
2024-05-27  7:50 ` Build regressions/improvements in v6.10-rc1 Geert Uytterhoeven
2024-05-27  8:21   ` Geert Uytterhoeven
2024-05-30 16:48 ` Linux 6.10-rc1 Guenter Roeck
2024-06-13 11:09 ` Pavel Machek
2024-06-13 16:17   ` Linus Torvalds
2024-06-14  9:02     ` Pavel Machek
2024-06-14 16:21       ` Linus Torvalds
2024-06-14 17:04         ` Linus Torvalds
2024-06-14 20:13           ` Pavel Machek
2024-06-14 20:24           ` Pavel Machek
2024-06-17  9:27           ` Pavel Machek [this message]
2024-06-19 10:43             ` Pavel Machek
2024-06-19 15:52               ` Linus Torvalds
2024-07-08 12:03                 ` Pavel Machek
2024-06-19 16:52               ` Gerhard Stoiber

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=ZnABbKrIzmmEoFEV@duo.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=airlied@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=torvalds@linux-foundation.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 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.