From: Zhen Lei <thunder.leizhen@huawei.com>
To: Russell King <linux@armlinux.org.uk>,
Ard Biesheuvel <ardb@kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <patches@armlinux.org.uk>
Cc: Zhen Lei <thunder.leizhen@huawei.com>
Subject: [PATCH 0/2] ARM: Make the dumped instructions are consistent with the disassembled ones
Date: Mon, 28 Nov 2022 19:42:41 +0800 [thread overview]
Message-ID: <20221128114243.2042-1-thunder.leizhen@huawei.com> (raw)
v1:
1. Refactor dump_instr(): classify by thumb and arm, and then by user and kernel.
2. Use __mem_to_opcode_thumb16() or __mem_to_opcode_arm() to convert the
instruction to the correct byte order before outputting.
Zhen Lei (2):
ARM: Refactor dump_instr()
ARM: Make the dumped instructions are consistent with the disassembled
ones
arch/arm/kernel/traps.c | 25 ++++++++++++++-----------
1 file changed, 14 insertions(+), 11 deletions(-)
--
2.25.1
WARNING: multiple messages have this Message-ID (diff)
From: Zhen Lei <thunder.leizhen@huawei.com>
To: Russell King <linux@armlinux.org.uk>,
Ard Biesheuvel <ardb@kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <patches@armlinux.org.uk>
Cc: Zhen Lei <thunder.leizhen@huawei.com>
Subject: [PATCH 0/2] ARM: Make the dumped instructions are consistent with the disassembled ones
Date: Mon, 28 Nov 2022 19:42:41 +0800 [thread overview]
Message-ID: <20221128114243.2042-1-thunder.leizhen@huawei.com> (raw)
v1:
1. Refactor dump_instr(): classify by thumb and arm, and then by user and kernel.
2. Use __mem_to_opcode_thumb16() or __mem_to_opcode_arm() to convert the
instruction to the correct byte order before outputting.
Zhen Lei (2):
ARM: Refactor dump_instr()
ARM: Make the dumped instructions are consistent with the disassembled
ones
arch/arm/kernel/traps.c | 25 ++++++++++++++-----------
1 file changed, 14 insertions(+), 11 deletions(-)
--
2.25.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2022-11-28 11:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-28 11:42 Zhen Lei [this message]
2022-11-28 11:42 ` [PATCH 0/2] ARM: Make the dumped instructions are consistent with the disassembled ones Zhen Lei
2022-11-28 11:42 ` [PATCH 1/2] ARM: Refactor dump_instr() Zhen Lei
2022-11-28 11:42 ` Zhen Lei
2022-11-28 11:42 ` [PATCH 2/2] ARM: Make the dumped instructions are consistent with the disassembled ones Zhen Lei
2022-11-28 11:42 ` Zhen Lei
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=20221128114243.2042-1-thunder.leizhen@huawei.com \
--to=thunder.leizhen@huawei.com \
--cc=ardb@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=patches@armlinux.org.uk \
/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.