Re: [PATCH] x86, add hypervisor name to dump_stack() [v4]

2012-11-01 Thread Gleb Natapov
On Tue, Oct 30, 2012 at 04:26:33PM -0400, Prarit Bhargava wrote: > Debugging crash, panics, stack trace WARN_ONs, etc., from both virtual and > bare-metal boots can get difficult very quickly. While there are ways to > decipher the output and determine if the output is from a virtual guest, > the

Re: [PATCH] x86, add hypervisor name to dump_stack() [v4]

2012-10-30 Thread Borislav Petkov
On Tue, Oct 30, 2012 at 04:26:33PM -0400, Prarit Bhargava wrote: > Debugging crash, panics, stack trace WARN_ONs, etc., from both virtual and > bare-metal boots can get difficult very quickly. While there are ways to > decipher the output and determine if the output is from a virtual guest, > the

[PATCH] x86, add hypervisor name to dump_stack() [v4]

2012-10-30 Thread Prarit Bhargava
Debugging crash, panics, stack trace WARN_ONs, etc., from both virtual and bare-metal boots can get difficult very quickly. While there are ways to decipher the output and determine if the output is from a virtual guest, the in-kernel hypervisors now have a single registration point and set x86_hy