linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Adrian Hunter <adrian.hunter@intel.com>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
	linux-kernel@vger.kernel.org, David Ahern <dsahern@gmail.com>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Jiri Olsa <jolsa@redhat.com>, Mike Galbraith <efault@gmx.de>,
	Paul Mackerras <paulus@samba.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Stephane Eranian <eranian@google.com>,
	Ingo Molnar <mingo@kernel.org>
Subject: Re: [PATCH 8/9] perf tools: add kcore to the object code reading test
Date: Wed, 31 Jul 2013 00:17:24 +0300	[thread overview]
Message-ID: <51F82D64.5060609@intel.com> (raw)
In-Reply-To: <87vc3s1uxj.fsf@sejong.aot.lge.com>

On 30/07/2013 8:24 a.m., Namhyung Kim wrote:
> On Thu, 25 Jul 2013 17:01:29 +0300, Adrian Hunter wrote:
>> Make the "object code reading" test attempt to read from
>> kcore.
>>
>> The test uses objdump which struggles with kcore. i.e.
>> doesn't always work, sometimes takes a long time.
>> The test has been made to work around those issues.
>>
> [SNIP]
>
>> -	if (al.map->dso->symtab_type == DSO_BINARY_TYPE__KALLSYMS) {
>> +	if (al.map->dso->symtab_type == DSO_BINARY_TYPE__KALLSYMS&&
>> +	    !dso__is_kcore(al.map->dso)) {
>
> I was confused.  So this means that the symbols came from the kallsyms
> but actual binary data came from the kcore, right?

Yes

>
>
>>   		pr_debug("Unexpected kernel address - skipping\n");
>>   		return 0;
>>   	}
>
> [SNIP]
>> +
>> +	/* 2nd time through we just try kcore */
>> +	if (try_kcore&&  !have_kcore)
>> +		return TEST_CODE_READING_NO_KCORE;
>> +
>> +	/* No point getting kernel events if there is no kernel object */
>> +	if (!have_vmlinux&&  !have_kcore)
>>   		excl_kernel = true;
>>
>>   	threads = thread_map__new_by_tid(pid);
>> @@ -457,8 +502,12 @@ static int do_test_code_reading(void)
>>   	if (ret<  0)
>>   		goto out_err;
>>
>> -	if (!have_vmlinux)
>> +	if (!have_vmlinux&&  !have_kcore&&  !try_kcore)
>> +		err = TEST_CODE_READING_NO_KERNEL_OBJ;
>> +	else if (!have_vmlinux&&  !try_kcore)
>>   		err = TEST_CODE_READING_NO_VMLINUX;
>> +	else if (!have_kcore&&  try_kcore)
>> +		err = TEST_CODE_READING_NO_KCORE;
>
> It seems that the above line is not reachable since we already bailed
> out the second test if we don't have kcore.

Fixed in V2

>
>
>>   	else if (excl_kernel)
>>   		err = TEST_CODE_READING_NO_ACCESS;
>>   	else
>> @@ -485,7 +534,9 @@ int test__code_reading(void)
>>   {
>>   	int ret;
>>
>> -	ret = do_test_code_reading();
>> +	ret = do_test_code_reading(false);
>> +	if (!ret)
>
> Shouldn't it be
>
> 	if (ret)

No.  Zero is returned if vmlinux is found and the kernel is not 
excluded.  In all other cases, there is no point trying kcore.
Note if vmlinux is not found, then kcore will be tried the first
time around.

> ?
>
> Thanks,
> Namhyung
>
>
>> +		ret = do_test_code_reading(true);
>>
>>   	switch (ret) {
>>   	case TEST_CODE_READING_OK:
>> @@ -493,9 +544,15 @@ int test__code_reading(void)
>>   	case TEST_CODE_READING_NO_VMLINUX:
>>   		fprintf(stderr, " (no vmlinux)");
>>   		return 0;
>> +	case TEST_CODE_READING_NO_KCORE:
>> +		fprintf(stderr, " (no kcore)");
>> +		return 0;
>>   	case TEST_CODE_READING_NO_ACCESS:
>>   		fprintf(stderr, " (no access)");
>>   		return 0;
>> +	case TEST_CODE_READING_NO_KERNEL_OBJ:
>> +		fprintf(stderr, " (no kernel obj)");
>> +		return 0;
>>   	default:
>>   		return -1;
>>   	};


  reply	other threads:[~2013-07-30 21:17 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-25 14:01 [PATCH 0/9] perf tools: add support for reading object code Adrian Hunter
2013-07-25 14:01 ` [PATCH 1/9] perf tools: add test " Adrian Hunter
2013-07-29  6:28   ` Namhyung Kim
2013-07-30 21:11     ` Adrian Hunter
2013-07-31 17:43       ` Arnaldo Carvalho de Melo
2013-08-03 13:47         ` Adrian Hunter
2013-07-25 14:01 ` [PATCH 2/9] perf tools: load kernel maps before using Adrian Hunter
2013-07-25 20:10   ` Ingo Molnar
2013-07-25 14:01 ` [PATCH 3/9] perf tools: make it possible to read object code from vmlinux Adrian Hunter
2013-07-25 14:01 ` [PATCH 4/9] perf tools: adjust the vmlinux symtab matches kallsyms test Adrian Hunter
2013-07-25 14:01 ` [PATCH 5/9] perf tools: avoid SyS kernel syscall aliases Adrian Hunter
2013-07-25 14:01 ` [PATCH 6/9] perf tools: make it possible to read object code from kernel modules Adrian Hunter
2013-07-25 14:01 ` [PATCH 7/9] perf tools: add support for reading from /proc/kcore Adrian Hunter
2013-07-30  4:37   ` Namhyung Kim
2013-07-30 21:12     ` Adrian Hunter
2013-07-25 14:01 ` [PATCH 8/9] perf tools: add kcore to the object code reading test Adrian Hunter
2013-07-30  5:24   ` Namhyung Kim
2013-07-30 21:17     ` Adrian Hunter [this message]
2013-07-25 14:01 ` [PATCH 9/9] perf tools: allow annotation using /proc/kcore Adrian Hunter
2013-07-25 20:22 ` [PATCH 0/9] perf tools: add support for reading object code Ingo Molnar
2013-07-27 12:27 ` Jiri Olsa

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=51F82D64.5060609@intel.com \
    --to=adrian.hunter@intel.com \
    --cc=acme@ghostprotocols.net \
    --cc=dsahern@gmail.com \
    --cc=efault@gmx.de \
    --cc=eranian@google.com \
    --cc=fweisbec@gmail.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=namhyung@kernel.org \
    --cc=paulus@samba.org \
    --cc=peterz@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).