From: Stewart Smith <stewart@linux.vnet.ibm.com>
To: Vasant Hegde <hegdevasant@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 2/2] powerpc/powernv: Interface to add opal dump region
Date: Wed, 23 Jul 2014 22:33:05 +1000 [thread overview]
Message-ID: <m3a980i7b2.fsf@oc8180480414.ibm.com> (raw)
In-Reply-To: <20140723092525.5170.25926.stgit@hegdevasant.in.ibm.com>
Vasant Hegde <hegdevasant@linux.vnet.ibm.com> writes:
> PowerNV platform is capable of capturing host memory region when system
> crashes (because of host/firmware). We have new OPAL API to register
> memory region to be capture when system crashes.
>
> This patch adds support for new API and also registers kernel log
> buffer.
I think we do need a way to un-register regions, and I think this may be
important around kexec - unless the log buffer is in exactly the same
place, there's a window where we could dump some random memory contents
as kernel log buffer, probably causing some poor support person to
scratch their head for a good long while.
> +void __init opal_dump_region_init(void)
> +{
> + void *addr;
> + uint64_t size;
> + int rc;
> +
> + /* Register kernel log buffer */
> + addr = get_log_buf_addr();
> + size = get_log_buf_len();
> + rc = add_dump_region_entry(DUMP_REGION_LOG_BUF, addr, size);
> + if (rc)
> + pr_warn("DUMP: Failed to register kernel log buffer. "
> + "rc = %d\n", rc);
This is what's going to be printed in kernel log when running on OPAL
firmware that doesn't support that call. Does this include the first GA
release on POWER8 systems? If so, we probably want a nicer log message
pointing to the fact that firmware is too old to support that function.
prev parent reply other threads:[~2014-07-23 12:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-23 9:25 [PATCH 1/2] printk: Add function to return log buffer address and size Vasant Hegde
2014-07-23 9:25 ` [PATCH 2/2] powerpc/powernv: Interface to add opal dump region Vasant Hegde
2014-07-23 12:33 ` Stewart Smith [this message]
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=m3a980i7b2.fsf@oc8180480414.ibm.com \
--to=stewart@linux.vnet.ibm.com \
--cc=hegdevasant@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®