All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Hui Wang <hui.wang@canonical.com>
Cc: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>,
	mathieu.desnoyers@efficios.com, pjw@kernel.org,
	linux-trace-kernel@vger.kernel.org, shuah@kernel.org,
	wangfushuai@baidu.com, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH 1/2] ring-buffer: Fix event length with forced 8-byte alignment
Date: Wed, 10 Jun 2026 12:17:22 -0400	[thread overview]
Message-ID: <20260610121722.6909d3cf@robin> (raw)
In-Reply-To: <ea9d00cb-54c6-4635-aa13-e5a688375132@canonical.com>

On Tue, 9 Jun 2026 12:22:47 +0800
Hui Wang <hui.wang@canonical.com> wrote:

> Thanks for the pointer. I reverted my two patches and applied the patch 
> you referenced, but unfortunately it doesn't resolve the problem — the 
> testcase still fails in my environment (riscv64 kernel with 
> CONFIG_HAVE_64BIT_ALIGNED_ACCESS enabled).
> 
>  From what I can tell, that fix addresses a different problem than the 
> one I'm hitting: it targets a 64K page-size issue, whereas my failure is 
> caused by the 64-bit alignment requirement 
> (CONFIG_HAVE_64BIT_ALIGNED_ACCESS). So I don't think they're the same 
> root cause.
> 
> So can you please take a look at them again.

OK, taking a deeper look at it, and yes, your are correct. Sorry for
jumping to the conclusion with thinking this was the same issue as what
was brought up before.

I'll take these.

Thanks,

-- Steve

  reply	other threads:[~2026-06-10 16:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-07  7:24 [PATCH 0/2] ring-buffer: Fix forced 8-byte alignment event length Hui Wang
2026-06-07  7:24 ` [PATCH 1/2] ring-buffer: Fix event length with forced 8-byte alignment Hui Wang
2026-06-08  9:02   ` Masami Hiramatsu
2026-06-08 16:52     ` Steven Rostedt
2026-06-09  4:22       ` Hui Wang
2026-06-10 16:17         ` Steven Rostedt [this message]
2026-06-07  7:24 ` [PATCH 2/2] selftests/ftrace: Account for 8-byte aligned trace_marker_raw events Hui Wang
2026-06-08  9:17   ` Masami Hiramatsu
2026-06-08 14:51     ` Hui Wang
2026-06-08 16:50   ` Steven Rostedt

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=20260610121722.6909d3cf@robin \
    --to=rostedt@goodmis.org \
    --cc=hui.wang@canonical.com \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mhiramat@kernel.org \
    --cc=pjw@kernel.org \
    --cc=shuah@kernel.org \
    --cc=wangfushuai@baidu.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 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.