From: "Zhouyi Zhou" <yizhouzhou@ict.ac.cn>
To: "Florian Westphal" <fw@strlen.de>
Cc: "Zhouyi Zhou" <zhouzhouyi@gmail.com>,
pablo@netfilter.org, kaber@trash.net, kadlec@blackhole.kfki.hu,
davem@davemloft.net, netfilter-devel@vger.kernel.org,
coreteam@netfilter.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, jbaron@akamai.com
Subject: Re: [PATCH 1/1] netfilter/jump_label: use HAVE_JUMP_LABEL?
Date: Thu, 21 Aug 2014 20:53:19 +0800 (GMT+08:00) [thread overview]
Message-ID: <1498523.4b875.147f8a0e3c8.Coremail.yizhouzhou@ict.ac.cn> (raw)
In-Reply-To: <20140821121132.GA16498@breakpoint.cc>
Thanks Florian for reviewing
> -----Original Messages-----
> From: "Florian Westphal" <fw@strlen.de>
>
> Zhouyi Zhou <zhouzhouyi@gmail.com> wrote:
> >
> > CONFIG_JUMP_LABEL doesn't ensure HAVE_JUMP_LABEL, if it
> > is not the case use maintainers's own mutex to guard
> > the modification of global values.
CONFIG_JUMP_LABEL says the user wants to use jump labels.
But we also need the toolchain to support it.
That is reflected in CC_HAVE_ASM_GOTO=y, and if both are
set then HAVE_JUMP_LABEL is set to true.
> I don't understand this patch.
>
> What is the problem you are fixing?
There is basically no real problem here.
This patch only tries to make kernel code that using
static_key infrastructure appears "unified"
>
> The intent is to only use static_key infrastructure
> if user has enabled CONFIG_JUMP_LABEL.
The other parts of kernel either use #ifdef HAVE_JUMP_LABEL,
or use no "#ifdef" at all(the two exceptions are netfilter
and powerpc modules which I send patches to both).
Jason has suggested me to make the patches:
https://lkml.org/lkml/2014/8/20/761
"Unified" is the reason, I guess :-)
so rookies like me can have unified examples to follow
Cheers
Zhouyi
next prev parent reply other threads:[~2014-08-21 12:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-21 2:52 Zhouyi Zhou
2014-08-21 12:11 ` Florian Westphal
2014-08-21 12:53 ` Zhouyi Zhou [this message]
2014-08-21 15:24 ` Florian Westphal
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=1498523.4b875.147f8a0e3c8.Coremail.yizhouzhou@ict.ac.cn \
--to=yizhouzhou@ict.ac.cn \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=fw@strlen.de \
--cc=jbaron@akamai.com \
--cc=kaber@trash.net \
--cc=kadlec@blackhole.kfki.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=zhouzhouyi@gmail.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
all inboxes | Powered by JetHome®