On Sun, Apr 07, 2013 at 01:38:48PM +0200, Jan Kiszka wrote:
> On 2013-04-07 13:37, Gleb Natapov wrote:
> > On Sun, Apr 07, 2013 at 01:33:05PM +0200, Jan Kiszka wrote:
> >> On 2013-02-27 12:19, Gleb Natapov wrote:
> >>> On Sat, Feb 23, 2013 at 05:05:29PM +0100, Jan Kiszka wrote:
> From: Jan Kis
On 2013-04-07 13:37, Gleb Natapov wrote:
> On Sun, Apr 07, 2013 at 01:33:05PM +0200, Jan Kiszka wrote:
>> On 2013-02-27 12:19, Gleb Natapov wrote:
>>> On Sat, Feb 23, 2013 at 05:05:29PM +0100, Jan Kiszka wrote:
From: Jan Kiszka
This fixes boot lockups with "no-kvmclock", when the ho
On Sun, Apr 07, 2013 at 01:33:05PM +0200, Jan Kiszka wrote:
> On 2013-02-27 12:19, Gleb Natapov wrote:
> > On Sat, Feb 23, 2013 at 05:05:29PM +0100, Jan Kiszka wrote:
> >> From: Jan Kiszka
> >>
> >> This fixes boot lockups with "no-kvmclock", when the host is not
> >> exposing this particular feat
On 2013-02-27 12:19, Gleb Natapov wrote:
> On Sat, Feb 23, 2013 at 05:05:29PM +0100, Jan Kiszka wrote:
>> From: Jan Kiszka
>>
>> This fixes boot lockups with "no-kvmclock", when the host is not
>> exposing this particular feature (QEMU: -cpu ...,-kvmclock) or when
>> the kvmclock initialization fa
On Sat, Feb 23, 2013 at 05:05:29PM +0100, Jan Kiszka wrote:
> From: Jan Kiszka
>
> This fixes boot lockups with "no-kvmclock", when the host is not
> exposing this particular feature (QEMU: -cpu ...,-kvmclock) or when
> the kvmclock initialization failed for whatever reason.
>
> Signed-off-by: J
On Sat, Feb 23, 2013 at 05:05:29PM +0100, Jan Kiszka wrote:
> From: Jan Kiszka
>
> This fixes boot lockups with "no-kvmclock", when the host is not
> exposing this particular feature (QEMU: -cpu ...,-kvmclock) or when
> the kvmclock initialization failed for whatever reason.
>
> Signed-off-by: J
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sorry, $subject reflects only half of the fix (v0.1, when I thought
hunk #2 would suffice). A better headline:
"x86: kvmclock: Fix boot with kvmclock disabled or not existing"
If you want me to resend, let me know.
Jan
On 2013-02-23 17:05, Jan Kisz
From: Jan Kiszka
This fixes boot lockups with "no-kvmclock", when the host is not
exposing this particular feature (QEMU: -cpu ...,-kvmclock) or when
the kvmclock initialization failed for whatever reason.
Signed-off-by: Jan Kiszka
---
Should go to 3.8 as well, I presume.
arch/x86/kernel/kvm