From: Robert Richter <robert.richter@amd.com>
To: Heinz Graalfs <graalfs@linux.vnet.ibm.com>
Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
"mingo@elte.hu" <mingo@elte.hu>,
"oprofile-list@lists.sf.net" <oprofile-list@lists.sf.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-s390@vger.kernel.org" <linux-s390@vger.kernel.org>,
"borntraeger@de.ibm.com" <borntraeger@de.ibm.com>
Subject: Re: [patch v2 0/3] OProfile support for System z's hardware sampling
Date: Tue, 15 Feb 2011 18:29:06 +0100 [thread overview]
Message-ID: <20110215172906.GG5874@erda.amd.com> (raw)
In-Reply-To: <1297789169.3231.9.camel@BR8HFPP0.boeblingen.de.ibm.com>
On 15.02.11 11:59:29, Heinz Graalfs wrote:
> > * Merge init.c and hwsampler_file.c, two files are bloated here and
> > hwsampler_file.c is a bad and too long naming.
> >
>
> OK, I've merged all hwsampler_files.c contents into init.c
>
> > * Rework functions in cpu_buffer.c (log_sample,
> > __oprofile_add_ext_sample, oprofile_add_ext_hw_sample, etc.). All
> > the (static) functions can be merged to a single functino by
> > implementing a struct that holds all current function arguments.
> > Something like:
> >
> > static void __oprofile_add_ext_sample(struct *foobar fb);
> > void oprofile_add_sample(struct pt_regs * const regs, unsigned long event)
> > {
> > struct foobar fb = { .regs = regs, .event = event };
> > __oprofile_add_ext_sample(&fb);
> > }
>
> OK, I've done this
>
> >
> > The naming and description of oprofile_add_ext_hw_sample() is also
> > not the best. As interface in include/linux/oprofile.h we could then
> > merge oprofile_add_ext_sample() and oprofile_add_ext_hw_sample() to
> > a single function.
> >
> > It would be nice if you could implement this.
>
> sure, I will do this, however I'm not sure what you exactly mean.
> Could you specify the interface in oprofile.h what you basically have in
> mind?
I mean to replace oprofile_add_ext_sample() and
oprofile_add_ext_hw_sample() by a new one. The interface would be in
the form of:
struct foobar {
...
}
static void __oprofile_add_ext_sample(struct *foobar fb);
Hope this makes sense. The advantage would be that we don't need to
extend the functions argument list anymore, we simply extend the
struct.
Please send me delta patches to oprofile/s390.
-Robert
--
Advanced Micro Devices, Inc.
Operating System Research Center
prev parent reply other threads:[~2011-02-15 17:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-21 10:06 [patch v2 0/3] OProfile support for System z's hardware sampling Heinz Graalfs
2011-01-21 10:06 ` [patch v2 1/3] This patch adds support for hardware based sampling on System z processors (models z10 and up) Heinz Graalfs
2011-02-14 18:57 ` Robert Richter
2011-03-25 11:00 ` Robert Richter
2011-03-29 12:38 ` Heinz Graalfs
2011-01-21 10:06 ` [patch v2 2/3] This patch enhances OProfile to support System zs hardware sampling feature Heinz Graalfs
2011-02-14 19:01 ` Robert Richter
2011-02-14 19:03 ` Robert Richter
2011-02-14 19:05 ` [PATCH] oprofile, s390: Rework hwsampler implementation Robert Richter
2011-02-14 19:07 ` [PATCH] oprofile, s390: Fix section mismatch of function hws_cpu_callback() Robert Richter
2011-01-21 10:06 ` [patch v2 3/3] This patch introduces a new oprofile sample add function (oprofile_add_ext_hw_sample) Heinz Graalfs
2011-02-14 18:55 ` Robert Richter
2011-02-07 8:23 ` [patch v2 0/3] OProfile support for System z's hardware sampling Heinz Graalfs
2011-02-14 19:42 ` Robert Richter
2011-02-15 7:17 ` Heiko Carstens
2011-02-15 16:59 ` Heinz Graalfs
2011-02-15 17:29 ` Robert Richter [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=20110215172906.GG5874@erda.amd.com \
--to=robert.richter@amd.com \
--cc=borntraeger@de.ibm.com \
--cc=graalfs@linux.vnet.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=oprofile-list@lists.sf.net \
--cc=schwidefsky@de.ibm.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