All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hemant <hkshaw@linux.vnet.ibm.com>
To: Namhyung Kim <namhyung@kernel.org>
Cc: linux-kernel@vger.kernel.org, srikar@linux.vnet.ibm.com,
	peterz@infradead.org, oleg@redhat.com, mingo@redhat.com,
	anton@redhat.com, systemtap@sourceware.org,
	masami.hiramatsu.pt@hitachi.com
Subject: Re: [PATCH 1/2] SDT markers listing by perf
Date: Fri, 06 Sep 2013 14:11:28 +0530	[thread overview]
Message-ID: <52299538.8040500@linux.vnet.ibm.com> (raw)
In-Reply-To: <87fvtisbej.fsf@sejong.aot.lge.com>

Hi Namhyung,

On 09/06/2013 12:07 PM, Namhyung Kim wrote:
> Hi Hemant,
>
> On Wed, 04 Sep 2013 23:07:57 +0530, Hemant wrote:
>> On 09/04/2013 12:12 PM, Namhyung Kim wrote:
>>> On Tue, 03 Sep 2013 13:06:55 +0530, Hemant Kumar wrote:
>>>> +	/*
>>>> +	 * Look for Section type = SHT_NOTE, flags = no SHF_ALLOC
>>>> +	 * and name = .note.stapsdt
>>>> +	 */
>>>> +	scn = elf_section_by_name(elf, &ehdr, &shdr, NOTE_SCN, NULL);
>>>> +	if (scn == NULL) {
>>>> +		pr_err("%s section not found!\n", NOTE_SCN);
>>>> +		goto out_end;
>>>> +	}
>>>> +
>>>> +	if (!(shdr.sh_type == SHT_NOTE) || (shdr.sh_flags & SHF_ALLOC))
>>>> +		goto out_end;
>>>> +
>>>> +	data = elf_getdata(scn, NULL);
>>>> +
>>>> +	/* Get the notes */
>>>> +	for (offset = 0; (next = gelf_getnote(data, offset, &nhdr, &name_off,
>>>> +					      &desc_off)) > 0; offset = next) {
>>>> +		tmp = populate_note(&elf, (const char *)((long)(data->d_buf) +
>>>> +							 (long)desc_off),
>>>> +				    nhdr.n_descsz, nhdr.n_type);
>>> Shouldn't we check the name of note being "stapsdt" as well as version
>>> (type) 3?
>> Since, we are already fetching the section NOTE_SCN (".note.stapsdt")
>> and then we check for the type being SHT_NOTE and SHF_ALLOC, is it
>> required to do the same for the individual notes?
> I don't know.  Now it seems only includes SDT notes with name being
> "stapsdt" and type being 3.  But things can be changed in future..
>
> Thanks,
> Namhyung
>

Yeah that may be a case. Ok, will put a check on the individual markers 
for their type.

Thanks
Hemant


  reply	other threads:[~2013-09-06  8:41 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-03  7:36 [RFC PATCH 0/2] Perf support to SDT markers Hemant Kumar Shaw
2013-09-03  7:36 ` [PATCH 1/2] SDT markers listing by perf Hemant Kumar
2013-09-03  8:19   ` Hemant
2013-09-04  6:43     ` Namhyung Kim
2013-09-04 17:40       ` Hemant
2013-09-04  6:42   ` Namhyung Kim
2013-09-04  8:01     ` Masami Hiramatsu
2013-09-04 17:58       ` Hemant
2013-09-15 11:28       ` Hemant
2013-09-25  4:37         ` Masami Hiramatsu
2013-09-25  6:03           ` Hemant
2013-09-25  8:45             ` Masami Hiramatsu
2013-09-04 17:37     ` Hemant
2013-09-06  6:37       ` Namhyung Kim
2013-09-06  8:41         ` Hemant [this message]
2013-09-04  7:21   ` Masami Hiramatsu
2013-09-04 17:52     ` Hemant
2013-09-03  7:37 ` [PATCH 2/2] Support to perf to probe on SDT markers: Hemant Kumar
2013-09-03  9:14   ` Masami Hiramatsu
2013-09-04  7:00   ` Namhyung Kim
2013-09-04  8:10     ` Masami Hiramatsu
2013-09-04 18:00       ` Hemant
2013-09-04 17:50     ` Hemant
2013-09-03  8:25 ` [RFC PATCH 0/2] Perf support to SDT markers Ingo Molnar
2013-09-03  9:17   ` Masami Hiramatsu
2013-09-03 13:23     ` Hemant
2013-09-03 14:21       ` Ingo Molnar
2013-09-03 15:11         ` Mark Wielaard
2013-09-03 19:24           ` Ingo Molnar
2013-09-03 15:24         ` Hemant
2013-09-04  6:49       ` Namhyung Kim
2013-09-04  8:22         ` Masami Hiramatsu
2013-09-04  8:25         ` Mark Wielaard
2013-09-04  8:39           ` Masami Hiramatsu
2013-09-04 18:08             ` Hemant
2013-09-05  4:59               ` Masami Hiramatsu
2013-09-04 18:12           ` Hemant
2013-09-04 18:52             ` Mark Wielaard
2013-09-04 20:39               ` Hemant
2013-09-04 17:45         ` Hemant
2013-09-04  6:08 ` Namhyung Kim
2013-09-04 17:08   ` Hemant
2013-09-04 23:41 ` Andi Kleen

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=52299538.8040500@linux.vnet.ibm.com \
    --to=hkshaw@linux.vnet.ibm.com \
    --cc=anton@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masami.hiramatsu.pt@hitachi.com \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=oleg@redhat.com \
    --cc=peterz@infradead.org \
    --cc=srikar@linux.vnet.ibm.com \
    --cc=systemtap@sourceware.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.