mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Valdis.Kletnieks@vt.edu
Cc: Beth Kon <eak@us.ibm.com>,
	rostedt@goodmis.org, Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org
Subject: Re: Wierdness - linux-next KVM patch breaks Dell Latitude D820, KVM not in kernel
Date: Sun, 13 Sep 2009 14:39:29 +0300	[thread overview]
Message-ID: <4AACD9F1.4000908@redhat.com> (raw)
In-Reply-To: <125228.1252788933@turing-police.cc.vt.edu>

On 09/12/2009 11:55 PM, Valdis.Kletnieks@vt.edu wrote:
> On Wed, 09 Sep 2009 14:59:12 EDT, Valdis.Kletnieks@vt.edu said:
>
>    
>> So hopefully excluding kvm.git I'll track down the *original* hang...
>>
>> Wish me luck. ;)
>>      
> And luck was not to be had.  Apparently 'git bisect skip' has some bad O(n**2)
> issues - I tried to exclude the kvm.git tree, and it ended up running literally
> overnight with no signs of stopping (see the gory details here:
> https://bugzilla.redhat.com/show_bug.cgi?id=522599 )  Now, I probably *could*
> cobble up something to do the skip as a series of little 20-40 commit skips,
> but that's just getting nuts. ;)
>
> Given that I'm having little luck bisecting this issue in linux-next and
> we're now into the merge window, does anybody have a *better* idea than letting
> the issue get into Linus's tree around -rc1, and hope that bisects more nicely
> than linux-next did, so -rc2 has a fix for it?
>    

Current linux-next should now be easily bisectable without the kvm.git 
issues you encountered.

-- 
error compiling committee.c: too many arguments to function


  reply	other threads:[~2009-09-13 11:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-07 14:07 Valdis.Kletnieks
2009-09-08 13:32 ` Beth Kon
2009-09-08 19:41   ` Valdis.Kletnieks
2009-09-09 14:25     ` Avi Kivity
2009-09-09 17:34     ` Valdis.Kletnieks
2009-09-09 17:38       ` Avi Kivity
2009-09-09 18:59         ` Valdis.Kletnieks
2009-09-12 20:55           ` Valdis.Kletnieks
2009-09-13 11:39             ` Avi Kivity [this message]
2009-09-20 15:50 ` Valdis.Kletnieks

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=4AACD9F1.4000908@redhat.com \
    --to=avi@redhat.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=akpm@linux-foundation.org \
    --cc=eak@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.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

Powered by JetHome