From: Rusty Russell <rusty@rustcorp.com.au>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: Kyle McMartin <kyle@redhat.com>,
"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Will Deacon <Will.Deacon@arm.com>,
"linux-arm-kernel\@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] aarch64: filter $x from kallsyms
Date: Wed, 15 Oct 2014 15:32:30 +1030 [thread overview]
Message-ID: <87oateapsp.fsf@rustcorp.com.au> (raw)
In-Reply-To: <20140925101417.GG10390@e104818-lin.cambridge.arm.com>
Catalin Marinas <catalin.marinas@arm.com> writes:
> On Thu, Sep 18, 2014 at 05:18:57AM +0100, Rusty Russell wrote:
>> Kyle McMartin <kyle@redhat.com> writes:
>> > Similar to ARM, AArch64 is generating $x and $d syms... which isn't
>> > terribly helpful when looking at %pF output and the like. Filter those
>> > out in kallsyms, modpost and when looking at module symbols.
>> >
>> > Seems simplest since none of these check EM_ARM anyway, to just add it
>> > to the strchr used, rather than trying to make things overly
>> > complicated.
>> >
>> > initcall_debug improves:
>> > dmesg_before.txt: initcall $x+0x0/0x154 [sg] returned 0 after 26331 usecs
>> > dmesg_after.txt: initcall init_sg+0x0/0x154 [sg] returned 0 after 15461 usecs
>> >
>> > Signed-off-by: Kyle McMartin <kyle@redhat.com>
>>
>> Acked-by: Rusty Russell <rusty@rustcorp.com.au>
>
> Thanks. Shall I understand that you are ok for me to take it via the
> arm64 tree (or you'd prefer to merge it via your tree)?
Sorry, vacation. Yes, it was all yours, and I see it in Linus' tree
now.
Thanks,
Rusty.
prev parent reply other threads:[~2014-10-15 6:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-16 21:37 [PATCH] aarch64: filter $x from kallsyms Kyle McMartin
2014-09-18 4:18 ` Rusty Russell
2014-09-25 10:14 ` Catalin Marinas
2014-10-15 5:02 ` Rusty Russell [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=87oateapsp.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=Will.Deacon@arm.com \
--cc=catalin.marinas@arm.com \
--cc=kyle@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.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