linux-hyperv.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Olaf Hering <olaf@aepfle.de>
To: Joseph Salisbury <joseph.salisbury@microsoft.com>,
	kys@microsoft.com, haiyangz@microsoft.com,
	sthemmin@microsoft.com, mikelley@microsoft.com
Cc: wei.liu@kernel.org, linux-hyperv@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Drivers: hv: Change flag to write log level in panic msg to false
Date: Fri, 10 Jul 2020 11:24:40 +0200	[thread overview]
Message-ID: <20200710092440.GA16562@aepfle.de> (raw)
In-Reply-To: <1593193685-74615-1-git-send-email-joseph.salisbury@microsoft.com>

[-- Attachment #1: Type: text/plain, Size: 722 bytes --]

On Fri, Jun 26, Joseph Salisbury wrote:

> When the kernel panics, one page worth of kmsg data is written to an allocated
> page.  The Hypervisor is notified of the page address trough the MSR.  This
> panic information is collected on the host.  Since we are only collecting one
> page of data, the full panic message may not be collected.

Are the people who need to work with this tiny bit of information
satisfied already, or did they already miss info even with this patch?

I'm asking because kmsg_dump_get_buffer unconditionally includes the
timestamp (unless it is enabled). I do wonder if there should be an API
addition to omit the timestamp. Then even more dmesg output can be
written into the 4k buffer.

Olaf

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2020-07-10  9:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-26 17:48 [PATCH] Drivers: hv: Change flag to write log level in panic msg to false Joseph Salisbury
2020-06-26 20:53 ` Michael Kelley
2020-06-26 22:15   ` Joseph Salisbury
2020-06-26 22:23     ` Michael Kelley
2020-06-26 22:25       ` Joseph Salisbury
2020-07-01 19:33 ` Sasha Levin
2020-07-10  9:24 ` Olaf Hering [this message]
2020-07-10 10:10   ` Michael Kelley

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=20200710092440.GA16562@aepfle.de \
    --to=olaf@aepfle.de \
    --cc=haiyangz@microsoft.com \
    --cc=joseph.salisbury@microsoft.com \
    --cc=kys@microsoft.com \
    --cc=linux-hyperv@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikelley@microsoft.com \
    --cc=sthemmin@microsoft.com \
    --cc=wei.liu@kernel.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;
as well as URLs for NNTP newsgroup(s).