All of lore.kernel.org
 help / color / mirror / Atom feed
From: Xianting Tian <xianting.tian@linux.alibaba.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>,
	paul.walmsley@sifive.com, palmer@dabbelt.com,
	aou@eecs.berkeley.edu, anup@brainfault.org, heiko@sntech.de,
	guoren@kernel.org, mick@ics.forth.gr,
	alexandre.ghiti@canonical.com, bhe@redhat.com, vgoyal@redhat.com,
	dyoung@redhat.com, corbet@lwn.net, Conor.Dooley@microchip.com,
	k-hagio-ab@nec.com, lijiang@redhat.com
Cc: kexec@lists.infradead.org, linux-doc@vger.kernel.org,
	linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
	crash-utility@redhat.com, heinrich.schuchardt@canonical.com,
	hschauhan@nulltrace.org, yixun.lan@gmail.com
Subject: Re: [PATCH V4 2/2] Documentation: kdump: describe VMCOREINFO export for RISCV64
Date: Thu, 20 Oct 2022 10:26:27 +0800	[thread overview]
Message-ID: <cc713fb3-371f-ffb9-d0d3-6bb4da776398@linux.alibaba.com> (raw)
In-Reply-To: <26810115-1325-faf2-0f6e-0d7ff164982d@gmail.com>


在 2022/10/20 上午9:56, Bagas Sanjaya 写道:
> On 10/19/22 17:36, Xianting Tian wrote:
>> The following interrelated definitions and ranges are needed by the kdump
>> crash tool, which are exported by "arch/riscv/kernel/crash_core.c":
>>      VA_BITS,
>>      PAGE_OFFSET,
>>      phys_ram_base,
>>      KERNEL_LINK_ADDR,
>>      MODULES_VADDR ~ MODULES_END,
>>      VMALLOC_START ~ VMALLOC_END,
>>      VMEMMAP_START ~ VMEMMAP_END,
>>
>> Document these RISCV64 exports above.
>>
>> Signed-off-by: Xianting Tian <xianting.tian@linux.alibaba.com>
> Hi Xianting,
>
> Seems like you forgot to keep carrying my Reviewed-by from v3 [1].
> Anyway, here it goes...
>
> Reviewed-by: Bagas Sanjaya <bagasdotme@gmail.com>
Sorry, I forgot... :(
>
> Thanks.
>
> [1]: https://lore.kernel.org/linux-doc/20221018081755.6214-3-xianting.tian@linux.alibaba.com/
>

WARNING: multiple messages have this Message-ID (diff)
From: Xianting Tian <xianting.tian@linux.alibaba.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>,
	paul.walmsley@sifive.com, palmer@dabbelt.com,
	aou@eecs.berkeley.edu, anup@brainfault.org, heiko@sntech.de,
	guoren@kernel.org, mick@ics.forth.gr,
	alexandre.ghiti@canonical.com, bhe@redhat.com, vgoyal@redhat.com,
	dyoung@redhat.com, corbet@lwn.net, Conor.Dooley@microchip.com,
	k-hagio-ab@nec.com, lijiang@redhat.com
Cc: kexec@lists.infradead.org, linux-doc@vger.kernel.org,
	linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
	crash-utility@redhat.com, heinrich.schuchardt@canonical.com,
	hschauhan@nulltrace.org, yixun.lan@gmail.com
Subject: Re: [PATCH V4 2/2] Documentation: kdump: describe VMCOREINFO export for RISCV64
Date: Thu, 20 Oct 2022 10:26:27 +0800	[thread overview]
Message-ID: <cc713fb3-371f-ffb9-d0d3-6bb4da776398@linux.alibaba.com> (raw)
In-Reply-To: <26810115-1325-faf2-0f6e-0d7ff164982d@gmail.com>


在 2022/10/20 上午9:56, Bagas Sanjaya 写道:
> On 10/19/22 17:36, Xianting Tian wrote:
>> The following interrelated definitions and ranges are needed by the kdump
>> crash tool, which are exported by "arch/riscv/kernel/crash_core.c":
>>      VA_BITS,
>>      PAGE_OFFSET,
>>      phys_ram_base,
>>      KERNEL_LINK_ADDR,
>>      MODULES_VADDR ~ MODULES_END,
>>      VMALLOC_START ~ VMALLOC_END,
>>      VMEMMAP_START ~ VMEMMAP_END,
>>
>> Document these RISCV64 exports above.
>>
>> Signed-off-by: Xianting Tian <xianting.tian@linux.alibaba.com>
> Hi Xianting,
>
> Seems like you forgot to keep carrying my Reviewed-by from v3 [1].
> Anyway, here it goes...
>
> Reviewed-by: Bagas Sanjaya <bagasdotme@gmail.com>
Sorry, I forgot... :(
>
> Thanks.
>
> [1]: https://lore.kernel.org/linux-doc/20221018081755.6214-3-xianting.tian@linux.alibaba.com/
>

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

WARNING: multiple messages have this Message-ID (diff)
From: Xianting Tian <xianting.tian@linux.alibaba.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>,
	paul.walmsley@sifive.com, palmer@dabbelt.com,
	aou@eecs.berkeley.edu, anup@brainfault.org, heiko@sntech.de,
	guoren@kernel.org, mick@ics.forth.gr,
	alexandre.ghiti@canonical.com, bhe@redhat.com, vgoyal@redhat.com,
	dyoung@redhat.com, corbet@lwn.net, Conor.Dooley@microchip.com,
	k-hagio-ab@nec.com, lijiang@redhat.com
Cc: kexec@lists.infradead.org, linux-doc@vger.kernel.org,
	linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
	crash-utility@redhat.com, heinrich.schuchardt@canonical.com,
	hschauhan@nulltrace.org, yixun.lan@gmail.com
Subject: Re: [PATCH V4 2/2] Documentation: kdump: describe VMCOREINFO export for RISCV64
Date: Thu, 20 Oct 2022 10:26:27 +0800	[thread overview]
Message-ID: <cc713fb3-371f-ffb9-d0d3-6bb4da776398@linux.alibaba.com> (raw)
In-Reply-To: <26810115-1325-faf2-0f6e-0d7ff164982d@gmail.com>


在 2022/10/20 上午9:56, Bagas Sanjaya 写道:
> On 10/19/22 17:36, Xianting Tian wrote:
>> The following interrelated definitions and ranges are needed by the kdump
>> crash tool, which are exported by "arch/riscv/kernel/crash_core.c":
>>      VA_BITS,
>>      PAGE_OFFSET,
>>      phys_ram_base,
>>      KERNEL_LINK_ADDR,
>>      MODULES_VADDR ~ MODULES_END,
>>      VMALLOC_START ~ VMALLOC_END,
>>      VMEMMAP_START ~ VMEMMAP_END,
>>
>> Document these RISCV64 exports above.
>>
>> Signed-off-by: Xianting Tian <xianting.tian@linux.alibaba.com>
> Hi Xianting,
>
> Seems like you forgot to keep carrying my Reviewed-by from v3 [1].
> Anyway, here it goes...
>
> Reviewed-by: Bagas Sanjaya <bagasdotme@gmail.com>
Sorry, I forgot... :(
>
> Thanks.
>
> [1]: https://lore.kernel.org/linux-doc/20221018081755.6214-3-xianting.tian@linux.alibaba.com/
>

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

  reply	other threads:[~2022-10-20  2:26 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-19 10:36 [PATCH V4 0/2] Support VMCOREINFO export for RISCV64 Xianting Tian
2022-10-19 10:36 ` Xianting Tian
2022-10-19 10:36 ` Xianting Tian
2022-10-19 10:36 ` [PATCH V4 1/2] RISC-V: Add arch_crash_save_vmcoreinfo support Xianting Tian
2022-10-19 10:36   ` Xianting Tian
2022-10-19 10:36   ` Xianting Tian
2022-10-20  2:08   ` Baoquan He
2022-10-20  2:08     ` Baoquan He
2022-10-20  2:08     ` Baoquan He
2022-10-20  2:17     ` Xianting Tian
2022-10-20  2:17       ` Xianting Tian
2022-10-20  2:17       ` Xianting Tian
2022-10-20  3:05       ` Baoquan He
2022-10-20  3:05         ` Baoquan He
2022-10-20  3:05         ` Baoquan He
2022-10-20  4:40         ` Xianting Tian
2022-10-20  4:40           ` Xianting Tian
2022-10-20  4:40           ` Xianting Tian
2022-10-26  9:08           ` Xianting Tian
2022-10-26  9:08             ` Xianting Tian
2022-10-26  9:08             ` Xianting Tian
2022-10-26  9:25             ` Conor Dooley
2022-10-26  9:25               ` Conor Dooley
2022-10-26  9:25               ` Conor Dooley
2022-10-26  9:44               ` Xianting Tian
2022-10-26  9:44                 ` Xianting Tian
2022-10-26  9:44                 ` Xianting Tian
2022-10-26 12:05                 ` Baoquan He
2022-10-26 12:05                   ` Baoquan He
2022-10-26 12:05                   ` Baoquan He
2022-10-26 13:47                   ` Conor Dooley
2022-10-26 13:47                     ` Conor Dooley
2022-10-26 13:47                     ` Conor Dooley
2022-10-26 14:24                     ` Xianting Tian
2022-10-26 14:24                       ` Xianting Tian
2022-10-26 14:24                       ` Xianting Tian
2022-10-31  8:57                     ` Baoquan He
2022-10-31  8:57                       ` Baoquan He
2022-10-31  8:57                       ` Baoquan He
2022-10-31  9:10                       ` Xianting Tian
2022-10-31  9:10                         ` Xianting Tian
2022-10-31  9:10                         ` Xianting Tian
2022-10-26 14:22                   ` Xianting Tian
2022-10-26 14:22                     ` Xianting Tian
2022-10-26 14:22                     ` Xianting Tian
2022-10-20 14:35   ` Guo Ren
2022-10-20 14:35     ` Guo Ren
2022-10-20 14:35     ` Guo Ren
2022-10-19 10:36 ` [PATCH V4 2/2] Documentation: kdump: describe VMCOREINFO export for RISCV64 Xianting Tian
2022-10-19 10:36   ` Xianting Tian
2022-10-19 10:36   ` Xianting Tian
2022-10-20  1:56   ` Bagas Sanjaya
2022-10-20  1:56     ` Bagas Sanjaya
2022-10-20  1:56     ` Bagas Sanjaya
2022-10-20  2:26     ` Xianting Tian [this message]
2022-10-20  2:26       ` Xianting Tian
2022-10-20  2:26       ` 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=cc713fb3-371f-ffb9-d0d3-6bb4da776398@linux.alibaba.com \
    --to=xianting.tian@linux.alibaba.com \
    --cc=Conor.Dooley@microchip.com \
    --cc=alexandre.ghiti@canonical.com \
    --cc=anup@brainfault.org \
    --cc=aou@eecs.berkeley.edu \
    --cc=bagasdotme@gmail.com \
    --cc=bhe@redhat.com \
    --cc=corbet@lwn.net \
    --cc=crash-utility@redhat.com \
    --cc=dyoung@redhat.com \
    --cc=guoren@kernel.org \
    --cc=heiko@sntech.de \
    --cc=heinrich.schuchardt@canonical.com \
    --cc=hschauhan@nulltrace.org \
    --cc=k-hagio-ab@nec.com \
    --cc=kexec@lists.infradead.org \
    --cc=lijiang@redhat.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=mick@ics.forth.gr \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=vgoyal@redhat.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 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.