From: "Jan Beulich" <JBeulich@novell.com>
To: "Jiri Slaby" <jslaby@suse.cz>
Cc: "Tim Deegan" <Tim.Deegan@citrix.com>,
"Jeremy Fitzhardinge" <jeremy@goop.org>,
<akpm@linux-foundation.org>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] fix jiffy calculations in calibrate_delay_direct to handle overflow
Date: Wed, 09 Feb 2011 13:18:41 +0000 [thread overview]
Message-ID: <4D52A241020000780003107A@vpn.id2.novell.com> (raw)
In-Reply-To: <4D52641E.9020001@suse.cz>
>>> On 09.02.11 at 10:53, Jiri Slaby <jslaby@suse.cz> wrote:
> On 02/09/2011 10:44 AM, Jan Beulich wrote:
>>>>> On 09.02.11 at 10:21, Jiri Slaby <jslaby@suse.cz> wrote:
>>> On 02/09/2011 09:31 AM, Jan Beulich wrote:
>>>> Fixes a hang when booting as dom0 under Xen, when jiffies can be
>>>> quite large by the time the kernel init gets this far.
>>>
>>> As I wrote this might happen if the boot till this point takes ~ 5
>>> minutes because we start at -5 minutes.
>>>
>>> That said, is this a candidate for stable? (If so, please CC stable.)
>>
>> Honestly, I'm not certain (given that mainline Xen Dom0 support
>> is still only in its beginnings).
>
> What about other VMs? If I run few non-kvm qemu VMs (kvm presets lpj) on
> a busy dual-core machine, this will be a problem too, right?
Yes, quite possible indeed.
Jan
next prev parent reply other threads:[~2011-02-09 13:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-09 8:31 [PATCH] fix jiffy calculations in calibrate_delay_direct to handle overflow Jan Beulich
2011-02-09 9:21 ` Jiri Slaby
2011-02-09 9:44 ` Jan Beulich
2011-02-09 9:53 ` Jiri Slaby
2011-02-09 13:18 ` Jan Beulich [this message]
2011-02-09 18:48 ` Jeremy Fitzhardinge
2011-02-09 20:54 ` Linus Torvalds
2011-02-10 8:48 ` Jan Beulich
2011-02-10 8:50 Jan Beulich
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=4D52A241020000780003107A@vpn.id2.novell.com \
--to=jbeulich@novell.com \
--cc=Tim.Deegan@citrix.com \
--cc=akpm@linux-foundation.org \
--cc=jeremy@goop.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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.