From: Jan Kiszka <jan.kiszka@web.de>
To: Gleb Natapov <gleb@redhat.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>, kvm <kvm@vger.kernel.org>
Subject: Re: [PATCH] x86: kvmclock: Do not setup kvmclock vsyscall in the absence of that clock
Date: Sun, 07 Apr 2013 13:38:48 +0200 [thread overview]
Message-ID: <51615AC8.8030308@web.de> (raw)
In-Reply-To: <20130407113709.GQ17919@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 842 bytes --]
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 <jan.kiszka@siemens.com>
>>>>
>>>> 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 <jan.kiszka@siemens.com>
>>> Applied, thanks.
>>
>> Just noticed that this fix isn't in Linus tree yet, thus also not yet in
>> 3.8.y. Which route does it take?
>>
> It is scheduled to go into 3.10. To get it into 3.8.y we need to send it
> to stable@.
Hmm, it's a bug fix for an ugly early kernel crash...
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
next prev parent reply other threads:[~2013-04-07 11:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-23 16:05 [PATCH] x86: kvmclock: Do not setup kvmclock vsyscall in the absence of that clock Jan Kiszka
2013-02-23 16:20 ` Jan Kiszka
2013-02-26 2:22 ` Marcelo Tosatti
2013-02-27 11:19 ` Gleb Natapov
2013-04-07 11:33 ` Jan Kiszka
2013-04-07 11:37 ` Gleb Natapov
2013-04-07 11:38 ` Jan Kiszka [this message]
2013-04-07 11:45 ` Gleb Natapov
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=51615AC8.8030308@web.de \
--to=jan.kiszka@web.de \
--cc=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.