From: Omar Sandoval <osandov@osandov.com>
To: Alexander Gordeev <agordeev@linux.ibm.com>
Cc: "Petr Tesařík" <petr@tesarici.cz>,
linux-s390@vger.kernel.org,
"Ilya Leoshkevich" <iii@linux.ibm.com>,
linux-debuggers@vger.kernel.org
Subject: Re: Incorrect vmcoreinfo KERNELOFFSET after "s390/boot: Rework deployment of the kernel image"
Date: Fri, 12 Jul 2024 07:17:38 -0700 [thread overview]
Message-ID: <ZpE7AsR-nD2tNuTn@telecaster> (raw)
In-Reply-To: <ZpEyucQA1rctAts6@li-008a6a4c-3549-11b2-a85c-c5cc2836eea2.ibm.com>
On Fri, Jul 12, 2024 at 03:42:17PM +0200, Alexander Gordeev wrote:
> On Thu, Jul 11, 2024 at 04:30:22PM -0700, Omar Sandoval wrote:
> Hi Omar,
> ...
> > I'd be really grateful if KERNELOFFSET was always the difference between
> > addresses in the kernel image and in memory like it is on other
> > architectures, or even if there was another, s390x-specific field in
> > vmcoreinfo for that.
>
> Do you mean another s390x-specific field that would be the same
> as KERNELOFFSET on other architectures?
Yeah. I'd still prefer if KERNELOFFSET itself was updated, but if that's
really not an option, another field could be a workaround.
Thanks,
Omar
next prev parent reply other threads:[~2024-07-12 14:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-20 23:34 Incorrect vmcoreinfo KERNELOFFSET after "s390/boot: Rework deployment of the kernel image" Omar Sandoval
2024-06-24 13:29 ` Alexander Gordeev
2024-06-27 13:51 ` Alexander Gordeev
2024-07-09 19:21 ` Petr Tesařík
2024-07-09 20:55 ` Omar Sandoval
2024-07-10 5:02 ` Petr Tesařík
2024-07-10 8:56 ` Alexander Gordeev
2024-07-11 23:55 ` Omar Sandoval
2024-07-10 8:53 ` Alexander Gordeev
2024-07-11 23:30 ` Omar Sandoval
2024-07-12 13:42 ` Alexander Gordeev
2024-07-12 14:17 ` Omar Sandoval [this message]
2024-07-15 10:06 ` Alexander Gordeev
2024-08-26 8:22 ` Alexander Gordeev
2024-08-27 19:38 ` Omar Sandoval
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=ZpE7AsR-nD2tNuTn@telecaster \
--to=osandov@osandov.com \
--cc=agordeev@linux.ibm.com \
--cc=iii@linux.ibm.com \
--cc=linux-debuggers@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=petr@tesarici.cz \
/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