From: Robert Richter <robert.richter@amd.com>
To: Mike Frysinger <vapier.adi@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>,
oprofile-list <oprofile-list@lists.sourceforge.net>,
Heinz Graalfs <graalfs@linux.vnet.ibm.com>
Subject: Re: [PATCH 2/2] oprofile: Add __exit attibute to oprofile_arch_exit() functions
Date: Thu, 17 Mar 2011 12:41:40 +0100 [thread overview]
Message-ID: <20110317114140.GA31407@erda.amd.com> (raw)
In-Reply-To: <AANLkTi=g-Dd957gPxCUfRxVw52T2m6GbswapEAJLnBtP@mail.gmail.com>
On 16.03.11 16:15:49, Mike Frysinger wrote:
> On Wed, Mar 16, 2011 at 13:58, Robert Richter wrote:
> > 979048e oprofile: don't call arch exit code from init code on failure
> >
> > we may add __exit attibutes to oprofile_arch_exit() functions.
>
> i dont think this the way to go. how about updating one place
> (include/linux/oprofile.h:oprofile_arch_exit) and making sure all arch
> files are including that header if they arent already ? after all, if
> they arent including that header, the arch code could break without
> noticing.
Mike,
do you mean we specify the __exit attribute in the function
declaration of the header file and make sure it is included
everythere? I was looking at current implementations in the kernel and
this is not common. Mostly the attributes are set in the function
definition. So I was not sure if that would work. If so, may we skip
then the __exit attribute in the definition?
GCC doc states: "The keyword __attribute__ allows you to specify
special attributes when making a declaration."
http://gcc.gnu.org/onlinedocs/gcc-4.5.1/gcc/Function-Attributes.html#Function%20Attributes
but nothing about that happens if it is in the function definition and
this is different from the declaration.
-Robert
--
Advanced Micro Devices, Inc.
Operating System Research Center
next prev parent reply other threads:[~2011-03-17 11:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-16 17:58 [PATCH 0/2] oprofile cleanups Robert Richter
2011-03-16 17:58 ` [PATCH 1/2] oprofile, s390: Cleanups Robert Richter
2011-03-16 17:58 ` [PATCH 2/2] oprofile: Add __exit attibute to oprofile_arch_exit() functions Robert Richter
2011-03-16 20:15 ` Mike Frysinger
2011-03-17 11:41 ` Robert Richter [this message]
2011-03-17 19:15 ` Mike Frysinger
2011-03-17 8:09 ` [PATCH 0/2] oprofile cleanups Ingo Molnar
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=20110317114140.GA31407@erda.amd.com \
--to=robert.richter@amd.com \
--cc=graalfs@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=oprofile-list@lists.sourceforge.net \
--cc=vapier.adi@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