From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Ryan Harper <ryanh-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: PATCH vmx.c: add printk_ratelimit in vmx_intr_assist
Date: Tue, 18 Dec 2007 18:30:55 +0200 [thread overview]
Message-ID: <4767F5BF.8000501@qumranet.com> (raw)
In-Reply-To: <20071214221359.GO23913-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Ryan Harper wrote:
> * Ryan Harper <ryanh-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org> [2007-12-14 09:36]:
>
>> * Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org> [2007-12-14 08:49]:
>>
>>> Ryan Harper wrote:
>>>
>>>> Add printk_ratelimit check in front of printk. This prevents spamming
>>>> of the message during 32-bit ubuntu 6.06server install. Previously, it
>>>> would hang during the partition formatting stage.
>>>>
>>>>
>>> Applied, but this is worrying. Do you know whether this is a regression?
>>>
>> I'll try out older releases to see if we did regress.
>>
>
> Looks like kvm-47 introduced the hang during format, -46 finishes the
> format just fine and with no printk spamming. I'll start seeing
> if I can bisect down to a particular changeset.
>
>
Unfortunately there was a window where interrupts were injected outside
the critical section, causing these errors. This was introduced in
kvm-47, so this doesn't help much.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services
for just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
prev parent reply other threads:[~2007-12-18 16:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-13 16:21 PATCH vmx.c: add printk_ratelimit in vmx_intr_assist Ryan Harper
[not found] ` <20071213162110.GJ23913-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2007-12-14 14:43 ` Avi Kivity
[not found] ` <476296A4.2010407-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-12-14 15:35 ` Ryan Harper
[not found] ` <20071214153527.GK23913-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2007-12-14 22:13 ` Ryan Harper
[not found] ` <20071214221359.GO23913-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2007-12-14 23:51 ` Ryan Harper
2007-12-18 16:30 ` Avi Kivity [this message]
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=4767F5BF.8000501@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=ryanh-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox