From: Thorsten Leemhuis <regressions@leemhuis.info>
To: regressions@lists.linux.dev
Cc: Paul Menzel <pmenzel@molgen.mpg.de>
Subject: Re: 100 ms boot time increase regression in acpi_init()/acpi_scan_bus() #forregzbot
Date: Fri, 18 Feb 2022 12:23:45 +0100 [thread overview]
Message-ID: <0debe946-9418-c8aa-9ba4-ecc77f8dac53@leemhuis.info> (raw)
In-Reply-To: <CAJZ5v0hyp1nR5id02abZh4cjw=sT0J_nf9spbUHfuwzjdJb5KA@mail.gmail.com>
TWIMC: this mail is primarily send for documentation purposes and for
regzbot, my Linux kernel regression tracking bot. These mails usually
contain '#forregzbot' in the subject, to make them easy to spot and filter.
On 08.02.22 18:59, Rafael J. Wysocki wrote:
> On Tue, Feb 8, 2022 at 1:03 PM Thorsten Leemhuis
> <regressions@leemhuis.info> wrote:
>>
>> Hi, this is your Linux kernel regression tracker speaking.
>>
>> Top-posting for once, to make this easy accessible to everyone.
>>
>> @Rafael or any other @acpi/@pm developer: what's the status here?
>> Neither in this thread nor in the bug ticket anything happened afaics.
>> Or is a 100ms boot time increase considered "not a regression"?
>
> It is on my list of things to look into, because it used to work
> faster, so depending on what change made it work slower, it may be
> possible to restore the previous performance without sacrificing too
> much.
>
> I honestly don't think that it is a noticeable issue for users in the
> field, though.
Great. FWIW, I'm putting this in regzbot on "backburner", as it's
something that shouldn't be forgotten, but is less urgent then other
regressions
#regzbot backburner: not that urgent, still on the developers's todo list
#regzbot ignore-activity
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
P.S.: As the Linux kernel's regression tracker I'm getting a lot of
reports on my table. I can only look briefly into most of them and lack
knowledge about most of the areas they concern. I thus unfortunately
will sometimes get things wrong or miss something important. I hope
that's not the case here; if you think it is, don't hesitate to tell me
in a public reply, it's in everyone's interest to set the public record
straight.
prev parent reply other threads:[~2022-02-18 11:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-10 11:29 100 ms boot time increase regression in acpi_init()/acpi_scan_bus() Paul Menzel
2022-01-31 7:36 ` Thorsten Leemhuis
2022-01-31 22:16 ` Bjorn Helgaas
2022-02-08 12:03 ` Thorsten Leemhuis
2022-02-08 17:59 ` Rafael J. Wysocki
2022-02-18 11:23 ` Thorsten Leemhuis [this message]
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=0debe946-9418-c8aa-9ba4-ecc77f8dac53@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=pmenzel@molgen.mpg.de \
--cc=regressions@lists.linux.dev \
/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;
as well as URLs for NNTP newsgroup(s).