All of lore.kernel.org
 help / color / mirror / Atom feed
From: Huang Shijie <shijie@os.amperecomputing.com>
To: kexec@lists.infradead.org
Subject: [PATCH] arm64: crash_core: Export MODULES, VMALLOC, and VMEMMAP ranges
Date: Thu, 17 Feb 2022 10:29:25 +0000	[thread overview]
Message-ID: <Yg4jhWnfYIGYBLs/@hsj> (raw)
In-Reply-To: <Yg4dDZGEyRzWcGH1@hsj>

On Thu, Feb 17, 2022 at 10:02:03AM +0000, Huang Shijie wrote:
> > Thanks for digging up all of the kernel memory map changes and taking the
> > time to explain the macros. However, all I'm really after is something in
> > the commit message of the patch which explains what is broken without this
> This kernel patch does not break anything.
I mean this kernel patch is not a bugfix, it is just make the ARM64 ecosystem
(including the Crash) a little better..

The Crash can just parse out the MODULES/VMALLOC/VMALLOC ranges from the vmcore file,
no need to calculate them in a very _hard_ way. 

Thanks
Huang Shijie


WARNING: multiple messages have this Message-ID (diff)
From: Huang Shijie <shijie@os.amperecomputing.com>
To: Will Deacon <will@kernel.org>
Cc: catalin.marinas@arm.com, bhe@redhat.com, vgoyal@redhat.com,
	dyoung@redhat.com, corbet@lwn.net, kexec@lists.infradead.org,
	linux-doc@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, zwang@amperecomputing.com,
	patches@amperecomputing.com, darren@os.amperecomputing.com,
	k-hagio-ab@nec.com, lijiang@redhat.com
Subject: Re: [PATCH] arm64: crash_core: Export MODULES, VMALLOC, and VMEMMAP ranges
Date: Thu, 17 Feb 2022 10:29:25 +0000	[thread overview]
Message-ID: <Yg4jhWnfYIGYBLs/@hsj> (raw)
In-Reply-To: <Yg4dDZGEyRzWcGH1@hsj>

On Thu, Feb 17, 2022 at 10:02:03AM +0000, Huang Shijie wrote:
> > Thanks for digging up all of the kernel memory map changes and taking the
> > time to explain the macros. However, all I'm really after is something in
> > the commit message of the patch which explains what is broken without this
> This kernel patch does not break anything.
I mean this kernel patch is not a bugfix, it is just make the ARM64 ecosystem
(including the Crash) a little better..

The Crash can just parse out the MODULES/VMALLOC/VMALLOC ranges from the vmcore file,
no need to calculate them in a very _hard_ way. 

Thanks
Huang Shijie

WARNING: multiple messages have this Message-ID (diff)
From: Huang Shijie <shijie@os.amperecomputing.com>
To: Will Deacon <will@kernel.org>
Cc: catalin.marinas@arm.com, bhe@redhat.com, vgoyal@redhat.com,
	dyoung@redhat.com, corbet@lwn.net, kexec@lists.infradead.org,
	linux-doc@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, zwang@amperecomputing.com,
	patches@amperecomputing.com, darren@os.amperecomputing.com,
	k-hagio-ab@nec.com, lijiang@redhat.com
Subject: Re: [PATCH] arm64: crash_core: Export MODULES, VMALLOC, and VMEMMAP ranges
Date: Thu, 17 Feb 2022 10:29:25 +0000	[thread overview]
Message-ID: <Yg4jhWnfYIGYBLs/@hsj> (raw)
In-Reply-To: <Yg4dDZGEyRzWcGH1@hsj>

On Thu, Feb 17, 2022 at 10:02:03AM +0000, Huang Shijie wrote:
> > Thanks for digging up all of the kernel memory map changes and taking the
> > time to explain the macros. However, all I'm really after is something in
> > the commit message of the patch which explains what is broken without this
> This kernel patch does not break anything.
I mean this kernel patch is not a bugfix, it is just make the ARM64 ecosystem
(including the Crash) a little better..

The Crash can just parse out the MODULES/VMALLOC/VMALLOC ranges from the vmcore file,
no need to calculate them in a very _hard_ way. 

Thanks
Huang Shijie

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

  reply	other threads:[~2022-02-17 10:29 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-09  9:26 [PATCH] arm64: crash_core: Export MODULES, VMALLOC, and VMEMMAP ranges Huang Shijie
2022-02-09  9:26 ` Huang Shijie
2022-02-09  9:26 ` Huang Shijie
2022-02-09  3:16 ` Baoquan He
2022-02-09  3:16   ` Baoquan He
2022-02-09  3:16   ` Baoquan He
2022-02-15 16:44 ` Will Deacon
2022-02-15 16:44   ` Will Deacon
2022-02-15 16:44   ` Will Deacon
2022-02-16  9:28   ` Huang Shijie
2022-02-16  9:28     ` Huang Shijie
2022-02-16  9:28     ` Huang Shijie
2022-02-16 12:40     ` Will Deacon
2022-02-16 12:40       ` Will Deacon
2022-02-16 12:40       ` Will Deacon
2022-02-17 10:01       ` Huang Shijie
2022-02-17 10:01         ` Huang Shijie
2022-02-17 10:01         ` Huang Shijie
2022-02-17 10:29         ` Huang Shijie [this message]
2022-02-17 10:29           ` Huang Shijie
2022-02-17 10:29           ` Huang Shijie
2022-03-07 22:03 ` Will Deacon
2022-03-07 22:03   ` Will Deacon
2022-03-07 22:03   ` Will Deacon

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=Yg4jhWnfYIGYBLs/@hsj \
    --to=shijie@os.amperecomputing.com \
    --cc=kexec@lists.infradead.org \
    /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.