> -----Original Message-----
> From: KY Srinivasan
> Sent: Monday, June 11, 2018 11:39 AM
> To: Sunil Muthuswamy <[email protected]>; Haiyang Zhang
> <[email protected]>
> Cc: [email protected]; Stephen Hemminger
> <[email protected]>
> Subject: RE: [PATCH v5] Drivers: HV: Send one page worth of kmsg dump
> over Hyper-V during panic
>
>
>
> > -----Original Message-----
> > From: Sunil Muthuswamy
> > Sent: Monday, June 11, 2018 10:44 AM
> > To: KY Srinivasan <[email protected]>; Haiyang Zhang
> > <[email protected]>
> > Cc: [email protected]; Stephen Hemminger
> > <[email protected]>
> > Subject: RE: [PATCH v5] Drivers: HV: Send one page worth of kmsg dump
> > over Hyper-V during panic
> >
> >
> >
> > > -----Original Message-----
> > > From: KY Srinivasan
> > > Sent: Sunday, June 10, 2018 2:54 PM
> > > To: Sunil Muthuswamy <[email protected]>; Haiyang Zhang
> > > <[email protected]>
> > > Cc: [email protected]; Stephen Hemminger
> > > <[email protected]>
> > > Subject: RE: [PATCH v5] Drivers: HV: Send one page worth of kmsg dump
> > > over Hyper-V during panic
> > >
> > >
> > >
> > > > -----Original Message-----
> > > > From: Sunil Muthuswamy
> > > > Sent: Friday, June 8, 2018 11:39 AM
> > > > To: Haiyang Zhang <[email protected]>
> > > > Cc: [email protected]; Sunil Muthuswamy
> > > > <[email protected]>; KY Srinivasan <[email protected]>;
> > Stephen
> > > > Hemminger <[email protected]>
> > > > Subject: [PATCH v5] Drivers: HV: Send one page worth of kmsg dump
> > over
> > > > Hyper-V during panic
> > > >
> > > > In the VM mode on Hyper-V, currently, when the kernel panics, an
> error
> > > > code and few register values are populated in an MSR and the
> Hypervisor
> > > > notified. This information is collected on the host. The amount of
> > > > information currently collected is found to be limited and not very
> > > > actionable. To gather more actionable data, such as stack trace, the
> > > > proposal is to write one page worth of kmsg data on an allocated page
> > > > and the Hypervisor notified of the page address through the MSR.
> > > >
>
> Snip.
>
> > > > /*
> > > > * vmbus_bus_init -Main vmbus driver initialization routine.
> > > > @@ -1065,6 +1136,38 @@ static int vmbus_bus_init(void)
> > > > * Only register if the crash MSRs are available
> > > > */
> > > > if (ms_hyperv.misc_features &
> > > > HV_FEATURE_GUEST_CRASH_MSR_AVAILABLE) {
> > > > + u64 hyperv_crash_ctl;
> > > > + if (!hv_ctl_table_hdr) {
> > > When vmus_bus_init is invoked, would hv_ctl_table_hdr ever be
> > > Non-NULL?
> Ping.
Missed this somehow. It should not be. Will fix this as well in the next
version.
>
> Snip.
>
> Regards,
>
> K. Y
_______________________________________________
devel mailing list
[email protected]
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
