On 06/24/2013 03:01 PM, Chegu Vinod wrote:
>
> Hello,
>
> Lots (~700+) of the following messages are showing up in the dmesg of a
> 3.10-rc1
> based kernel (Host OS is running on a large socket count box with HT-on).
>
> [ 82.270682] PERCPU: allocation failed, size=42 align=16, alloc from
x86_hyper. We can use this to output additional debug
information during a panic/oops/stack trace.
Signed-off-by: Prarit Bhargava
Cc: Avi Kivity
Cc: Gleb Natapov
Cc: Alex Williamson
Cc: Marcelo Tostatti
Cc: Ingo Molnar
Cc: kvm@vger.kernel.org
Cc: x...@kernel.org
[v2]: Modifications suggested by
On 10/30/2012 03:14 PM, 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,
> t
x86_hyper. We can use this to output additional debug
information during a panic/oops/stack trace.
Signed-off-by: Prarit Bhargava
Cc: Avi Kivity
Cc: Gleb Natapov
Cc: Alex Williamson
Cc: Marcelo Tostatti
Cc: Ingo Molnar
Cc: kvm@vger.kernel.org
Cc: x...@kernel.org
[v2]: Modifications suggested by
x86_hyper. We can use this to output additional debug
information during a panic/oops/stack trace.
Signed-off-by: Prarit Bhargava
Cc: Avi Kivity
Cc: Gleb Natapov
Cc: Alex Williamson
Cc: Marcelo Tostatti
Cc: Ingo Molnar
Cc: kvm@vger.kernel.org
Cc: x...@kernel.org
[v2]: Modifications suggested by
On 10/24/2012 05:49 AM, Ingo Molnar wrote:
>
> * 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 determ
x86_hyper. We can use this to output a single extra line on virtual
machines that indicates the hypervisor type.
Signed-off-by: Prarit Bhargava
Cc: Avi Kivity
Cc: Gleb Natapov
Cc: Alex Williamson
Cc: Marcelo Tostatti
Cc: Ingo Molnar
Cc: kvm@vger.kernel.org
Cc: x...@kernel.org
---
arch/x86/kernel
On 07/17/2012 10:42 PM, Ren, Yongjie wrote:
> kvm.git next branch
> commit: ebf7d2e9
>
> arch/x86/built-in.o: In function `init_hypervisor_platform':
> (.init.text+0x56b1): undefined reference to `x86_hyper_kvm'
> arch/x86/built-in.o: In function `init_hypervisor_platform':
> (.init.text+0x56bc)
On 07/17/2012 10:42 PM, Ren, Yongjie wrote:
> kvm.git next branch
> commit: ebf7d2e9
>
> arch/x86/built-in.o: In function `init_hypervisor_platform':
> (.init.text+0x56b1): undefined reference to `x86_hyper_kvm'
> arch/x86/built-in.o: In function `init_hypervisor_platform':
> (.init.text+0x56bc)
On 07/06/2012 07:27 AM, Marcelo Tosatti wrote:
> On Thu, Jul 05, 2012 at 09:37:00AM -0400, Prarit Bhargava wrote:
>>
>>
>> On 07/05/2012 09:26 AM, Avi Kivity wrote:
>>> Please copy at least kvm@vger.kernel.org, and preferably Marcelo as well
>>> (the other
hich is used in
detect_hypervisor_platform() which results in a nice printk in the
syslog. This is only really a stub function but it
does make kvm more consistent with the other hypervisors.
[v2]: add detect and _GPL export
Signed-off-by: Prarit Bhargava
Cc: Avi Kivity
Cc: Gleb Natapov
Cc: Ale
11 matches
Mail list logo