From: Thomas Gleixner <tglx@linutronix.de>
To: Enlin Mu <enlinmu@gmail.com>
Cc: Enlin Mu <enlin.mu@outlook.com>,
linux-kernel@vger.kernel.org, enlin.mu@unisoc.com,
linux-hardening@vger.kernel.org
Subject: Re: [PATCH] hrtimer:Add get_hrtimer_cpu_base()
Date: Fri, 15 Mar 2024 04:41:59 +0100 [thread overview]
Message-ID: <87h6h8kvp4.ffs@tglx> (raw)
In-Reply-To: <CAAfh-jM6TSbFHUYCi0kC7JgszCaz=-So7+=at-aDfTSrOPjraQ@mail.gmail.com>
On Fri, Mar 15 2024 at 11:12, Enlin Mu wrote:
> Thomas Gleixner <tglx@linutronix.de> 于2024年3月14日周四 19:59写道:
>>
>> On Thu, Mar 14 2024 at 18:45, Enlin Mu wrote:
>> > Thomas Gleixner <tglx@linutronix.de> 于2024年3月14日周四 18:22写道:
>> >>
>> >> On Wed, Mar 13 2024 at 05:30, Enlin Mu wrote:
>> >> > From: Enlin Mu <enlin.mu@unisoc.com>
>> >> >
>> >> > On the Arm platform,arch_timer may occur irq strom,
>> >> > By using the next_timer of hrtimer_cpu_base, it is
>> >> > possible to quickly locate abnormal timers.
>> >> > As it is an out of tree modules,the function needs
>> >> > to be exproted.
>> >>
>> >> No. We are not exporting for out of tree code.
>> > Can you explain it?
>>
>> Exporting functions or variables requires an in tree usecase.
>
> OK, Thanks, I got it.
No, you did not get it at all.
Q: Where is the actual in kernel use case which utilizes the exported
symbol in a module?
A: There is still none.
For further clarification there will be none ever because you are
violating all encapsulation rules of the kernel subsytems without
providing at least an attempt of justification.
Nothing outside of the timer core subsystem has any business to fiddle
with this data structure ever. Period.
prev parent reply other threads:[~2024-03-15 3:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-13 5:30 [PATCH] hrtimer:Add get_hrtimer_cpu_base() Enlin Mu
2024-03-14 10:22 ` Thomas Gleixner
2024-03-14 10:45 ` Enlin Mu
2024-03-14 11:59 ` Thomas Gleixner
2024-03-15 2:07 ` Enlin Mu
2024-03-15 2:20 ` Enlin Mu
2024-03-15 3:12 ` Enlin Mu
2024-03-15 3:41 ` Thomas Gleixner [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=87h6h8kvp4.ffs@tglx \
--to=tglx@linutronix.de \
--cc=enlin.mu@outlook.com \
--cc=enlin.mu@unisoc.com \
--cc=enlinmu@gmail.com \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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