mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Thomas Gleixner <tglx@linutronix.de>,
	Randy Dunlap <rdunlap@infradead.org>,
	linux-kernel@vger.kernel.org
Cc: Ulf Hansson <ulf.hansson@linaro.org>
Subject: Re: [PATCH] genirq/timings: add kernel-doc for a function param
Date: Wed, 15 Jan 2025 13:09:21 +0100	[thread overview]
Message-ID: <e6ef436f-9f18-408e-9b24-e6464176a0a5@linaro.org> (raw)
In-Reply-To: <87a5bscs82.ffs@tglx>

Hi Thomas,

[Cc'ed Ulf]

On 15/01/2025 10:59, Thomas Gleixner wrote:
> On Fri, Jan 10 2025 at 22:29, Randy Dunlap wrote:
> 
>> Add the description for @now to eliminate a kernel-doc warning.
>> (Is this function used? I don't see it being called.)
> 
> That's indeed a good question.
> 
> Daniel, what's the state of this after 7+ years of being in "comes soon"
> state?

We recently discussed that with Ulf.

The next irq prediction would greatly help during the DSU [1] shut down 
process. As the last CPU going down initiates the DSU shut down, there 
are no more IPI involved and the timer + irq prediction will be much 
more accurate.

However, it is clear that we are talking about this feature since a long 
time and we did not finish its implementation yet, so it is not really 
serious to ask for more retention in the kernel if it is unused.

On the other side, it took me a lot of effort to elaborate the suffix 
based algorithm for the prediction and it would be a pity if we drop it 
because of the lack of progress :(

So, here is my proposal. Ulf and I will do the changes for the DSU power 
down which is reasonable to say it can happen during the next cycle. If 
there is nothing for the end of the next cycle, then we remove the code.

Does it sound good ?



[1] https://developer.arm.com/Processors/DSU-120


-- 
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs

Follow Linaro:  <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog

  reply	other threads:[~2025-01-15 12:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-11  6:29 Randy Dunlap
2025-01-15  9:59 ` Thomas Gleixner
2025-01-15 12:09   ` Daniel Lezcano [this message]
2025-01-15 16:06     ` Thomas Gleixner
2025-01-15 19:03 ` [tip: irq/core] genirq/timings: Add kernel-doc for a function parameter tip-bot2 for Randy Dunlap
2025-01-15 20:47 ` tip-bot2 for Randy Dunlap

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=e6ef436f-9f18-408e-9b24-e6464176a0a5@linaro.org \
    --to=daniel.lezcano@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=ulf.hansson@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®