From: "HAGIO KAZUHITO(萩尾 一仁)" <k-hagio-ab@nec.com>
To: Xianting Tian <xianting.tian@linux.alibaba.com>
Cc: "linux-riscv@lists.infradead.org"
<linux-riscv@lists.infradead.org>,
"kexec@lists.infradead.org" <kexec@lists.infradead.org>,
"hschauhan@nulltrace.org" <hschauhan@nulltrace.org>,
"lifang_xia@linux.alibaba.com" <lifang_xia@linux.alibaba.com>,
"crash-utility@redhat.com" <crash-utility@redhat.com>,
"mick@ics.forth.gr" <mick@ics.forth.gr>,
"heinrich.schuchardt@canonical.com"
<heinrich.schuchardt@canonical.com>,
"guoren@kernel.org" <guoren@kernel.org>,
"yixun.lan@gmail.com" <yixun.lan@gmail.com>,
"lijiang@redhat.com" <lijiang@redhat.com>
Subject: Re: [Crash-utility][PATCH V4 1/9] Add RISCV64 framework code support
Date: Fri, 21 Oct 2022 02:57:25 +0000 [thread overview]
Message-ID: <b5209fda-17c2-9271-c40e-1a0343a725a2@nec.com> (raw)
In-Reply-To: <4bccb5c9-6385-23d9-d496-65f9bd06beb2@linux.alibaba.com>
On 2022/10/21 11:42, Xianting Tian wrote:
>
> 在 2022/10/21 上午10:17, HAGIO KAZUHITO(萩尾 一仁) 写道:
>> On 2022/10/20 10:50, Xianting Tian wrote:
>>
>>> diff --git a/README b/README
>>> index 5abbce1..d589e72 100644
>>> --- a/README
>>> +++ b/README
>>> @@ -37,7 +37,7 @@
>>> These are the current prerequisites:
>>> o At this point, x86, ia64, x86_64, ppc64, ppc, arm, arm64, alpha, mips,
>>> - mips64, s390 and s390x-based kernels are supported. Other architectures
>>> + mips64, riscv64, s390 and s390x-based kernels are supported. Other architectures
>>> may be addressed in the future.
>> Sentences in the README are wrapped within 80 characters, I will change
>
> thanks,
>
> Do you need me to send V5 patch set to fix this?
No, I will amend these when applying.
Thanks,
Kazu
>
>> this to:
>>
>> + mips64, riscv64, s390 and s390x-based kernels are supported. Other
>> + architectures may be addressed in the future.
>>
>>> o One size fits all -- the utility can be run on any Linux kernel version
>>> @@ -98,6 +98,8 @@
>>> arm64 dumpfiles may be built by typing "make target=ARM64".
>>> o On an x86_64 host, an x86_64 binary that can be used to analyze
>>> ppc64le dumpfiles may be built by typing "make target=PPC64".
>>> + o On an x86_64 host, an x86_64 binary that can be used to analyze
>>> + riscv64 dumpfiles may be built by typing "make target=RISCV64".
>>> Traditionally when vmcores are compressed via the makedumpfile(8) facility
>>> the libz compression library is used, and by default the crash utility
>>
>>> diff --git a/help.c b/help.c
>>> index 99214c1..253c71b 100644
>>> --- a/help.c
>>> +++ b/help.c
>>> @@ -9512,7 +9512,7 @@ char *README[] = {
>>> " These are the current prerequisites: ",
>>> "",
>>> " o At this point, x86, ia64, x86_64, ppc64, ppc, arm, arm64, alpha, mips,",
>>> -" mips64, s390 and s390x-based kernels are supported. Other architectures",
>>> +" mips64, riscv64, s390 and s390x-based kernels are supported. Other architectures",
>>> " may be addressed in the future.",
>>> "",
>>> " o One size fits all -- the utility can be run on any Linux kernel version",
>> Same as above.
>>
>> And help.c lacks this part, will add:
>>
>> @@ -9572,6 +9572,8 @@ README_ENTER_DIRECTORY,
>> " arm64 dumpfiles may be built by typing \"make target=ARM64\".",
>> " o On an x86_64 host, an x86_64 binary that can be used to analyze",
>> " ppc64le dumpfiles may be built by typing \"make target=PPC64\".",
>> +" o On an x86_64 host, an x86_64 binary that can be used to analyze",
>> +" riscv64 dumpfiles may be built by typing \"make target=RISCV64\".",
>> "",
>> " Traditionally when vmcores are compressed via the makedumpfile(8) facility",
>> " the libz compression library is used, and by default the crash utility",
>>
>>
>> With these, the v4 crash patch set looks good to me.
>>
>> Acked-by: Kazuhito Hagio <k-hagio-ab@nec.com>
>>
>> Thanks,
>> Kazu
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2022-10-21 2:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 1:50 [Crash-utility][PATCH V4 0/9] Support RISCV64 arch and common commands Xianting Tian
2022-10-20 1:50 ` [Crash-utility][PATCH V4 1/9] Add RISCV64 framework code support Xianting Tian
2022-10-21 2:17 ` HAGIO KAZUHITO(萩尾 一仁)
2022-10-21 2:42 ` Xianting Tian
2022-10-21 2:57 ` HAGIO KAZUHITO(萩尾 一仁) [this message]
2022-11-03 5:32 ` lijiang
2022-11-09 9:01 ` Xianting Tian
2022-12-22 4:48 ` HAGIO KAZUHITO(萩尾 一仁)
2022-10-20 1:50 ` [Crash-utility][PATCH V4 2/9] RISCV64: Make crash tool enter command line and support some commands Xianting Tian
2022-10-20 1:50 ` [Crash-utility][PATCH V4 3/9] RISCV64: Add 'dis' command support Xianting Tian
2022-10-20 1:50 ` [Crash-utility][PATCH V4 4/9] RISCV64: Add irq " Xianting Tian
2022-10-20 1:50 ` [Crash-utility][PATCH V4 5/9] RISCV64: Add 'bt' " Xianting Tian
2022-10-20 1:50 ` [Crash-utility][PATCH V4 6/9] RISCV64: Add 'help -r' " Xianting Tian
2022-10-20 1:50 ` [Crash-utility][PATCH V4 7/9] RISCV64: Add 'help -m/M' " Xianting Tian
2022-10-20 1:50 ` [Crash-utility][PATCH V4 8/9] RISCV64: Add 'mach' " Xianting Tian
2022-10-20 1:50 ` [Crash-utility][PATCH V4 9/9] RISCV64: Add the implementation of symbol verify Xianting Tian
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=b5209fda-17c2-9271-c40e-1a0343a725a2@nec.com \
--to=k-hagio-ab@nec.com \
--cc=crash-utility@redhat.com \
--cc=guoren@kernel.org \
--cc=heinrich.schuchardt@canonical.com \
--cc=hschauhan@nulltrace.org \
--cc=kexec@lists.infradead.org \
--cc=lifang_xia@linux.alibaba.com \
--cc=lijiang@redhat.com \
--cc=linux-riscv@lists.infradead.org \
--cc=mick@ics.forth.gr \
--cc=xianting.tian@linux.alibaba.com \
--cc=yixun.lan@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