From: Marc Zyngier <maz@kernel.org>
To: zc <zoucao@linux.alibaba.com>
Cc: tglx@linutronix.de, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, jason@lakedaemon.net
Subject: Re: [PATCH] irqchip/gic-v3: change gic_data into gic_v3_data
Date: Thu, 03 Sep 2020 11:12:14 +0100 [thread overview]
Message-ID: <b286343d4a17afea491c195920ca0c5d@kernel.org> (raw)
In-Reply-To: <69118106-e6d8-71dc-7004-80fd96b32e54@linux.alibaba.com>
On 2020-09-03 11:05, zc wrote:
> thank for you reply.
>
>
> of course it won't, i just think it is better to splite the
> global data between irq-gic and irq-gic-v3.
>
> I wrote some hook module for gic, kallsyms_lookup_name can't support
> for mutlipte symbol,
>
> i need to call kallsyms scan to get the addr.
Why would you need to hook into the GIC data?
> If you think it isn't necessary, well for me.
I don't think it is necessary for mainline to work correctly,
and I don't understand what you are trying to achieve with this
"hook module".
If you could explain what you are trying to do and why you are
doing it, maybe we can come up with something. But I don't
think blindly repainting symbol names is a sensible course of
action.
Thanks,
M.
--
Jazz is not dead. It just smells funny...
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2020-09-03 10:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-03 9:08 [PATCH] irqchip/gic-v3: change gic_data into gic_v3_data Zou Cao
2020-09-03 9:55 ` Marc Zyngier
2020-09-03 10:05 ` zc
2020-09-03 10:12 ` Marc Zyngier [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=b286343d4a17afea491c195920ca0c5d@kernel.org \
--to=maz@kernel.org \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=zoucao@linux.alibaba.com \
/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).