mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paolo Bonzini <bonzini@gnu.org>
To: zhenwei pi <pizhenwei@bytedance.com>,
	arnd@arndb.de, gregkh@linuxfoundation.org, peng.hao2@zte.com.cn
Cc: hutao@cn.fujitsu.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] misc: pvpanic: add crash loaded event
Date: Sat, 18 Jan 2020 21:56:29 +0100	[thread overview]
Message-ID: <4c94bd8c-6d53-b037-b8b3-b261fcb515e1@gnu.org> (raw)
In-Reply-To: <20191215034840.2273096-1-pizhenwei@bytedance.com>

On 15/12/19 04:48, zhenwei pi wrote:
> Add PVPANIC_CRASH_LOADED bit for pvpanic event, it means that guest
> kernel actually hit a kernel panic, but the guest kernel wants to
> handle by itself.
> 
> Suggested by Greg KH, move the bit definition to uapi header file
> for the programs outside of kernel.
> 
> zhenwei pi (2):
>   misc: pvpanic: move bit definition to uapi header file
>   misc: pvpanic: add crash loaded event
> 
>  drivers/misc/pvpanic.c      | 12 +++++++++---
>  include/uapi/misc/pvpanic.h |  9 +++++++++
>  2 files changed, 18 insertions(+), 3 deletions(-)
>  create mode 100644 include/uapi/misc/pvpanic.h
> 

Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>

  parent reply	other threads:[~2020-01-18 20:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-15  3:48 zhenwei pi
2019-12-15  3:48 ` [PATCH v2 1/2] misc: pvpanic: move bit definition to uapi header file zhenwei pi
2019-12-15  3:48 ` [PATCH v2 2/2] misc: pvpanic: add crash loaded event zhenwei pi
2020-01-18 20:56 ` Paolo Bonzini [this message]
2019-12-25  6:26 [PATCH v2 0/2] " zhenwei pi
2020-01-02  2:35 zhenwei pi

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=4c94bd8c-6d53-b037-b8b3-b261fcb515e1@gnu.org \
    --to=bonzini@gnu.org \
    --cc=arnd@arndb.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=hutao@cn.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peng.hao2@zte.com.cn \
    --cc=pizhenwei@bytedance.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

all inboxes | Powered by JetHome®