From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: kys@exchange.microsoft.com
Cc: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
devel@linuxdriverproject.org, olaf@aepfle.de, apw@canonical.com,
jasowang@redhat.com, leann.ogasawara@canonical.com,
marcelo.cerri@canonical.com, sthemmin@microsoft.com,
kys@microsoft.com
Subject: Re: [PATCH 3/3] Drivers: hv: vmbus: Make pannic reporting to be more useful
Date: Thu, 12 Oct 2017 15:39:37 +0200 [thread overview]
Message-ID: <87vajkcwo6.fsf@vitty.brq.redhat.com> (raw)
In-Reply-To: <20171006003506.24444-3-kys@exchange.microsoft.com> (kys@exchange.microsoft.com's message of "Thu, 5 Oct 2017 17:35:06 -0700")
kys@exchange.microsoft.com writes:
> From: "K. Y. Srinivasan" <kys@microsoft.com>
>
> Hyper-V allows the guest to report panic and the guest can pass additional
> information. All this is logged on the host. Currently Linux is passing back
> information that is not particularly useful. Make the following changes:
>
> 1. Windows uses crash MSR P0 to report bugcheck code. Follow the same
> convention for Linux as well.
> 2. It will be useful to know the gust ID of the Linux guest that has
> paniced. Pass back this information.
>
> These changes will help in better supporting Linux on Hyper-V
>
> Signed-off-by: K. Y. Srinivasan <kys@microsoft.com>
> ---
> arch/x86/hyperv/hv_init.c | 11 +++++++----
> arch/x86/include/asm/mshyperv.h | 2 +-
> drivers/hv/vmbus_drv.c | 4 ++--
> 3 files changed, 10 insertions(+), 7 deletions(-)
>
> diff --git a/arch/x86/hyperv/hv_init.c b/arch/x86/hyperv/hv_init.c
> index 1a8eb550c40f..cc30a094fb7c 100644
> --- a/arch/x86/hyperv/hv_init.c
> +++ b/arch/x86/hyperv/hv_init.c
> @@ -205,9 +205,10 @@ void hyperv_cleanup(void)
> }
> EXPORT_SYMBOL_GPL(hyperv_cleanup);
>
> -void hyperv_report_panic(struct pt_regs *regs)
> +void hyperv_report_panic(struct pt_regs *regs, long err)
> {
> static bool panic_reported;
> + u64 guest_id;
>
> /*
> * We prefer to report panic on 'die' chain as we have proper
> @@ -218,9 +219,11 @@ void hyperv_report_panic(struct pt_regs *regs)
> return;
> panic_reported = true;
>
> - wrmsrl(HV_X64_MSR_CRASH_P0, regs->ip);
> - wrmsrl(HV_X64_MSR_CRASH_P1, regs->ax);
> - wrmsrl(HV_X64_MSR_CRASH_P2, regs->bx);
> + rdmsrl(HV_X64_MSR_GUEST_OS_ID, guest_id);
> +
> + wrmsrl(HV_X64_MSR_CRASH_P0, err);
> + wrmsrl(HV_X64_MSR_CRASH_P1, guest_id);
This is a constant we write in hyperv_init() (0x810000040e000000 for
Linux guests). Do I get it right that we need this to basically
distinguigh Windows guests crashes from Linux guest crashes in the log?
> + wrmsrl(HV_X64_MSR_CRASH_P2, regs->ip);
> wrmsrl(HV_X64_MSR_CRASH_P3, regs->cx);
> wrmsrl(HV_X64_MSR_CRASH_P4, regs->dx);
We don't write ax and bx any more but write cx and dx. Not that I see
these regs really useful in the log but I'd change these to ax and bx
for consistency. Or mayme make it sp and ax?
>
> diff --git a/arch/x86/include/asm/mshyperv.h b/arch/x86/include/asm/mshyperv.h
> index 63cc96f064dc..dd2dc54ddf20 100644
> --- a/arch/x86/include/asm/mshyperv.h
> +++ b/arch/x86/include/asm/mshyperv.h
> @@ -311,7 +311,7 @@ static inline int hv_cpu_number_to_vp_number(int cpu_number)
> void hyperv_init(void);
> void hyperv_setup_mmu_ops(void);
> void hyper_alloc_mmu(void);
> -void hyperv_report_panic(struct pt_regs *regs);
> +void hyperv_report_panic(struct pt_regs *regs, long err);
> bool hv_is_hypercall_page_setup(void);
> void hyperv_cleanup(void);
> #else /* CONFIG_HYPERV */
> diff --git a/drivers/hv/vmbus_drv.c b/drivers/hv/vmbus_drv.c
> index e8cd19095212..852f6c628836 100644
> --- a/drivers/hv/vmbus_drv.c
> +++ b/drivers/hv/vmbus_drv.c
> @@ -65,7 +65,7 @@ static int hyperv_panic_event(struct notifier_block *nb, unsigned long val,
>
> regs = current_pt_regs();
>
> - hyperv_report_panic(regs);
> + hyperv_report_panic(regs, val);
> return NOTIFY_DONE;
> }
>
> @@ -75,7 +75,7 @@ static int hyperv_die_event(struct notifier_block *nb, unsigned long val,
> struct die_args *die = (struct die_args *)args;
> struct pt_regs *regs = die->regs;
>
> - hyperv_report_panic(regs);
> + hyperv_report_panic(regs, val);
> return NOTIFY_DONE;
> }
--
Vitaly
next prev parent reply other threads:[~2017-10-12 13:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-06 0:33 [PATCH 0/3] Drivers: hv: vmbus: Miscellaneous enhancements and fixes kys
2017-10-06 0:35 ` [PATCH 1/3] Drivers: hv: vmbus: Expose per-channel interrupts and events counters kys
2017-10-06 0:35 ` [PATCH 2/3] vmbus: initialize reserved fields in messages kys
2017-10-06 0:35 ` [PATCH 3/3] Drivers: hv: vmbus: Make pannic reporting to be more useful kys
2017-10-12 13:39 ` Vitaly Kuznetsov [this message]
2017-10-12 15:06 ` KY Srinivasan
2017-10-20 13:27 ` [PATCH 1/3] Drivers: hv: vmbus: Expose per-channel interrupts and events counters Greg KH
2017-10-20 13:28 ` [PATCH 0/3] Drivers: hv: vmbus: Miscellaneous enhancements and fixes Greg KH
2017-10-20 21:35 ` KY Srinivasan
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=87vajkcwo6.fsf@vitty.brq.redhat.com \
--to=vkuznets@redhat.com \
--cc=apw@canonical.com \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=jasowang@redhat.com \
--cc=kys@exchange.microsoft.com \
--cc=kys@microsoft.com \
--cc=leann.ogasawara@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.cerri@canonical.com \
--cc=olaf@aepfle.de \
--cc=sthemmin@microsoft.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