From: Ryan Harper <ryanh-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
To: Ryan Harper <ryanh-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Subject: Re: PATCH vmx.c: add printk_ratelimit in vmx_intr_assist
Date: Fri, 14 Dec 2007 17:51:29 -0600 [thread overview]
Message-ID: <20071214235129.GP23913@us.ibm.com> (raw)
In-Reply-To: <20071214221359.GO23913-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
* Ryan Harper <ryanh-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org> [2007-12-14 16:14]:
> * 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.
My git skills are poor and I can't for the life of my figure out how to
get kvm and kvm-userspace checked out at kvm-46 and build them together.
So, instead I tested the nightly tarballs between Oct 10 (kvm-46
release) and Oct 18 (kvm-47).
kvm-snapshot-20071014.tar.gz is the last known good version.
version: kvm-snapshot-20071014
srcversion: 5F6E5524AD0A76F65C4CF60
The flooding of: [2592349.069880] Fault when IDT_Vectoring starts with
1015 but 1015 can complete the formatting. 16 and 17 won't compile. 18
of course fails completely.
So, something between 14 and 15 added the flooding, and something
between 15 and 18 prevents formatting from progressing.
--
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
(512) 838-9253 T/L: 678-9253
ryanh-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org
-------------------------------------------------------------------------
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
next prev parent reply other threads:[~2007-12-14 23:51 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 [this message]
2007-12-18 16:30 ` Avi Kivity
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=20071214235129.GP23913@us.ibm.com \
--to=ryanh-r/jw6+rmf7hqt0dzr+alfa@public.gmane.org \
--cc=avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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