From: Michael Ellerman <mpe@ellerman.id.au>
To: Hari Bathini <hbathini@linux.vnet.ibm.com>,
linuxppc-dev <linuxppc-dev@ozlabs.org>
Cc: Mahesh J Salgaonkar <mahesh@linux.vnet.ibm.com>
Subject: Re: powerpc/kdump: skip enabling big endian exception during crash
Date: Fri, 12 Dec 2014 09:40:16 +1100 (AEDT) [thread overview]
Message-ID: <20141211224016.86E111400F1@ozlabs.org> (raw)
In-Reply-To: <20141211164454.4641.71441.stgit@localhost.localdomain>
On Thu, 2014-11-12 at 16:44:54 UTC, Hari Bathini wrote:
> In LE kernel, we currently have a hack for kexec that resets the exception endian
> before starting a new kernel as the kernel that is loaded could be a big endian
> or a little endian kernel. In kdump case, resetting exception endian fails when
> one or more cpus is disabled. But in case of kdump, we can conveniently ignore
> resetting endianess as crashkernel is always of same endianess as primary kernel.
No, it's not guaranteed to be the same endianess.
That tends to be what people do in practice, but it's not an assumption you can
hard code.
cheers
next prev parent reply other threads:[~2014-12-11 22:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-11 16:44 [PATCH] powerpc/kdump: skip enabling big endian exception during crash Hari Bathini
2014-12-11 22:40 ` Michael Ellerman [this message]
2014-12-12 4:06 ` Mahesh Jagannath Salgaonkar
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=20141211224016.86E111400F1@ozlabs.org \
--to=mpe@ellerman.id.au \
--cc=hbathini@linux.vnet.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=mahesh@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).