[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CABXGCsOxkM+ohzudsTg=e5x=UATArAx0zCLnGHFwHHXs9Rz6VA@mail.gmail.com>
Date: Tue, 30 Apr 2024 19:42:32 +0500
From: Mikhail Gavrilov <mikhail.v.gavrilov@...il.com>
To: Takashi Iwai <tiwai@...e.de>
Cc: Linux List Kernel Mailing <linux-kernel@...r.kernel.org>, linux-sound@...r.kernel.org
Subject: Re: regression/bisected/6.9 commit 587d67fd929ad89801bcc429675bda90d53f6592
decrease 30% of gaming performance
On Tue, Apr 30, 2024 at 5:12 PM Takashi Iwai <tiwai@...e.de> wrote:
> Where and how...? That important piece is missing in you info...
> And, it's likely a false-positive detection by lockdep.
>
> When you disable lockdep, does it still show any performance down?
Of course without "lockdep" performance is even better than the commit
587d67fd929a just reverted.
- mainline kernel without changes with lockdep - 13244 [1]
- mainline kernel with reverted 587d67fd929a with lockdep - 19218 [2]
- mainline kernel without changes without lockdep - 22440 [3]
I think I get what you're saying: after a false-positive detection,
lockdep is partially disabled. Yes?
How do I understand that lockdep has partially turned off?
I would expect to see such a message in the kernel log " INFO: lockdep
is turned off."
But in my case this message didn't appear.
In any case, sorry for wasting your time.
[1] https://postimg.cc/G4NPHMyk
[2] https://postimg.cc/1n0D7sYH
[3] https://postimg.cc/nMYHWRcF
--
Best Regards,
Mike Gavrilov.
Powered by blists - more mailing lists