From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: linuxppc-dev@lists.ozlabs.org, Michael Ellerman <mpe@ellerman.id.au>
Cc: npiggin@gmail.com
Subject: Re: [PATCH 1/2] powerpc: Make stack frame marker upper case
Date: Wed, 05 Oct 2022 00:26:05 +1100 [thread overview]
Message-ID: <166488996500.779920.5936049394897797698.b4-ty@ellerman.id.au> (raw)
In-Reply-To: <20220927150419.1503001-1-mpe@ellerman.id.au>
On Wed, 28 Sep 2022 01:04:18 +1000, Michael Ellerman wrote:
> Now that the stack frame regs marker is only 32-bits it is not as
> obvious in memory dumps and easier to miss, eg:
>
> c000000004733e40 0000000000000000 0000000000000000 |................|
> c000000004733e50 0000000000000000 0000000000000000 |................|
> c000000004733e60 0000000000000000 0000000000000000 |................|
> c000000004733e70 7367657200000000 0000000000000000 |sger............|
> c000000004733e80 a700000000000000 708897f7ff7f0000 |........p.......|
> c000000004733e90 0073428fff7f0000 208997f7ff7f0000 |.sB..... .......|
> c000000004733ea0 0100000000000000 ffffffffffffffff |................|
> c000000004733eb0 0000000000000000 0000000000000000 |................|
>
> [...]
Applied to powerpc/next.
[1/2] powerpc: Make stack frame marker upper case
https://git.kernel.org/powerpc/c/bbd71709087a9d486d1da42399eec14e106072f2
[2/2] powerpc: Reverse stack frame marker on little endian
https://git.kernel.org/powerpc/c/19c95df1277c48e3ef8cc7d9f1d315dce949f203
cheers
prev parent reply other threads:[~2022-10-04 13:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-27 15:04 [PATCH 1/2] powerpc: Make stack frame marker upper case Michael Ellerman
2022-09-27 15:04 ` [PATCH 2/2] powerpc: Reverse stack frame marker on little endian Michael Ellerman
2022-09-28 3:13 ` Nicholas Piggin
2022-10-04 13:26 ` Michael Ellerman [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=166488996500.779920.5936049394897797698.b4-ty@ellerman.id.au \
--to=patch-notifications@ellerman.id.au \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.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 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).