From: Steven Rostedt <rostedt@goodmis.org>
To: Jessica Clarke <jrtc27@jrtc27.com>
Cc: Anatoly Pugachev <matorola@gmail.com>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
Sparc kernel list <sparclinux@vger.kernel.org>,
Ingo Molnar <mingo@redhat.com>
Subject: Re: [sparc64] ftrace: kernel startup-tests unaligned access
Date: Mon, 14 Dec 2020 11:31:23 -0500 [thread overview]
Message-ID: <20201214113123.0b44e35e@gandalf.local.home> (raw)
In-Reply-To: <20201214162804.GA27786@Jessicas-MacBook.local>
On Mon, 14 Dec 2020 16:28:04 +0000
Jessica Clarke <jrtc27@jrtc27.com> wrote:
> On Mon, Dec 14, 2020 at 11:15:12AM -0500, Steven Rostedt wrote:
> > On Mon, 14 Dec 2020 18:59:02 +0300
> > Anatoly Pugachev <matorola@gmail.com> wrote:
> >
> > > Hello!
> > >
> > > Enabled ftrace startup tests on a sparc64 test VM/LDOM:
> > >
> > > $ diff -u <(gzip -dc ~/dmesg/config-5.10.0.gz) <(gzip -dc /proc/config.gz)
> > > --- /dev/fd/63 2020-12-14 16:19:38.239372599 +0300
> > > +++ /dev/fd/62 2020-12-14 16:19:38.235372433 +0300
> > > @@ -2842,7 +2842,10 @@
> > > # CONFIG_TRACEPOINT_BENCHMARK is not set
> > > # CONFIG_RING_BUFFER_BENCHMARK is not set
> > > # CONFIG_TRACE_EVAL_MAP_FILE is not set
> > > -# CONFIG_FTRACE_STARTUP_TEST is not set
> > > +CONFIG_FTRACE_SELFTEST=y
> > > +CONFIG_FTRACE_STARTUP_TEST=y
> > > +CONFIG_EVENT_TRACE_STARTUP_TEST=y
> > > +# CONFIG_EVENT_TRACE_TEST_SYSCALLS is not set
> > > # CONFIG_RING_BUFFER_STARTUP_TEST is not set
> > > # CONFIG_PREEMPTIRQ_DELAY_TEST is not set
> > > # CONFIG_KPROBE_EVENT_GEN_TEST is not set
> > >
> > >
> > > Got the following results with kernel boot logs:
> > >
> > > Dec 14 13:48:15 kernel: clocksource: jiffies: mask: 0xffffffff
> > > max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
> > > Dec 14 13:48:15 kernel: futex hash table entries: 65536 (order: 9,
> > > 4194304 bytes, linear)
> > > Dec 14 13:48:15 kernel: Running postponed tracer tests:
> > > Dec 14 13:48:15 kernel: Testing tracer function:
> > > Dec 14 13:48:15 kernel: Kernel unaligned access at TPC[552a20]
> > > trace_function+0x40/0x140
> > > Dec 14 13:48:15 kernel: Kernel unaligned access at TPC[552a24]
> > > trace_function+0x44/0x140
> > > Dec 14 13:48:15 kernel: Kernel unaligned access at TPC[552a20]
> > > trace_function+0x40/0x140
> > > Dec 14 13:48:15 kernel: Kernel unaligned access at TPC[552a24]
> > > trace_function+0x44/0x140
> > > Dec 14 13:48:15 kernel: Kernel unaligned access at TPC[552a20]
> > > trace_function+0x40/0x140
> >
> > Does sparc64 require 8 byte alignment for 8 byte words?
>
> Yes, SPARC requires natural alignment for all primitive types (and that
> even includes 8-byte alignment for 8-byte types on 32-bit SPARC as it
> has load/store pair instructions the compiler is free to use).
>
>
OK, that means I was misinformed about reverting the patch that forced
alignment (and the patch I posted in reply to my email, is the revert of
the revert).
If the patch I just posted works, then I'll get it ready for mainline and
stable.
Thanks!
-- Steve
prev parent reply other threads:[~2020-12-14 16:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-14 15:59 Anatoly Pugachev
2020-12-14 16:15 ` Steven Rostedt
2020-12-14 16:26 ` Steven Rostedt
2020-12-14 17:12 ` Anatoly Pugachev
2020-12-14 16:28 ` Jessica Clarke
2020-12-14 16:31 ` Steven Rostedt [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=20201214113123.0b44e35e@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=jrtc27@jrtc27.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matorola@gmail.com \
--cc=mingo@redhat.com \
--cc=sparclinux@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
all inboxes | Powered by JetHome®