From: Dou Liyang <douly.fnst@cn.fujitsu.com>
To: Thomas Gleixner <tglx@linutronix.de>,
Kees Cook <keescook@chromium.org>, <re.emese@gmail.com>,
Marc Zyngier <marc.zyngier@arm.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: irqdesc: Why the "__ref" is needed in __irq_alloc_descs() ?
Date: Fri, 9 Mar 2018 15:07:47 +0800 [thread overview]
Message-ID: <9246951e-9cf5-6a3f-5cf4-2d3aaff03026@cn.fujitsu.com> (raw)
Hi Maintainers,
I have a question about "__ref" in Linux kernel.
When I looked into the __irq_alloc_descs(), I found it tagged a
"__ref" mark, but I didn't find that it referenced code or data
from init section.
So, I confuse why the "__ref" is needed in __irq_alloc_descs()?
any other reasons?
And after I tested, seems "__ref" just puts the code into a different
section that is not checked by modpost. It does not affect the
performance whether it is tagged or not. Is it right?
Thanks,
dou.
next reply other threads:[~2018-03-09 7:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-09 7:07 Dou Liyang [this message]
2018-03-09 11:39 ` Thomas Gleixner
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=9246951e-9cf5-6a3f-5cf4-2d3aaff03026@cn.fujitsu.com \
--to=douly.fnst@cn.fujitsu.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=re.emese@gmail.com \
--cc=tglx@linutronix.de \
/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®