From: Avi Kivity <avi@redhat.com>
To: bugzilla-daemon@bugzilla.kernel.org,
Xiao Guangrong <xiaoguangrong@cn.fujitsu.com>
Cc: kvm@vger.kernel.org
Subject: Re: [Bug 37262] VNC access to KVM VM is unusable
Date: Thu, 16 Jun 2011 17:00:17 +0300 [thread overview]
Message-ID: <4DFA0C71.1020909@redhat.com> (raw)
In-Reply-To: <201106152144.p5FLibSN003523@demeter2.kernel.org>
On 06/16/2011 12:44 AM, bugzilla-daemon@bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=37262
>
>
>
>
>
> --- Comment #38 from Steve<stefan.bosak@gmail.com> 2011-06-15 21:44:37 ---
> I found it:
>
> 5d163b1c9d6e5562dcdfd6cd471f237f1502bb35 is the first bad commit
> commit 5d163b1c9d6e5562dcdfd6cd471f237f1502bb35
> Author: Xiao Guangrong<xiaoguangrong@cn.fujitsu.com>
> Date: Wed Mar 9 15:43:00 2011 +0800
>
> KVM: MMU: introduce a common function to get no-dirty-logged slot
>
> Cleanup the code of pte_prefetch_gfn_to_memslot and
> mapping_level_dirty_bitmap
>
> Signed-off-by: Xiao Guangrong<xiaoguangrong@cn.fujitsu.com>
> Signed-off-by: Avi Kivity<avi@redhat.com>
>
> :040000 040000 23f9e0cbbeba9b82067fc50ffc3fdd0c2982a206
> 28607b5635b3cb78048f9e270ddefde39f1ed25f M arch
>
Xiao? Can you take a look?
Steve, can you confirm by:
$ git bisect reset
$ git checkout 5d163b1c9d6e5562dc
[build and test, verify failure]
$ git checkout 5d163b1c9d6e5562dc^
[build and test, verify success]
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-06-16 14:00 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-11 20:04 [Bug 37262] New: VNC access to KVM VM is unusable bugzilla-daemon
2011-06-12 11:50 ` [Bug 37262] " bugzilla-daemon
2011-06-12 13:24 ` bugzilla-daemon
2011-06-12 13:42 ` bugzilla-daemon
2011-06-12 13:54 ` bugzilla-daemon
2011-06-12 13:57 ` bugzilla-daemon
2011-06-12 14:41 ` bugzilla-daemon
2011-06-12 14:43 ` bugzilla-daemon
2011-06-12 14:58 ` bugzilla-daemon
2011-06-12 15:00 ` bugzilla-daemon
2011-06-12 15:39 ` bugzilla-daemon
2011-06-12 15:39 ` bugzilla-daemon
2011-06-12 15:54 ` bugzilla-daemon
2011-06-12 15:55 ` bugzilla-daemon
2011-06-12 16:00 ` bugzilla-daemon
2011-06-12 16:11 ` bugzilla-daemon
2011-06-12 16:18 ` bugzilla-daemon
2011-06-12 16:23 ` bugzilla-daemon
2011-06-12 17:01 ` bugzilla-daemon
2011-06-12 19:30 ` bugzilla-daemon
2011-06-12 22:19 ` bugzilla-daemon
2011-06-12 22:46 ` bugzilla-daemon
2011-06-12 22:49 ` bugzilla-daemon
2011-06-12 22:58 ` bugzilla-daemon
2011-06-12 23:22 ` bugzilla-daemon
2011-06-13 8:11 ` bugzilla-daemon
2011-06-13 8:59 ` bugzilla-daemon
2011-06-13 8:59 ` bugzilla-daemon
2011-06-13 9:15 ` bugzilla-daemon
2011-06-13 9:22 ` bugzilla-daemon
2011-06-13 9:35 ` bugzilla-daemon
2011-06-13 9:55 ` bugzilla-daemon
2011-06-13 12:18 ` bugzilla-daemon
2011-06-13 14:05 ` bugzilla-daemon
2011-06-13 14:12 ` bugzilla-daemon
2011-06-13 14:27 ` bugzilla-daemon
2011-06-15 17:10 ` bugzilla-daemon
2011-06-15 17:19 ` bugzilla-daemon
2011-06-15 21:44 ` bugzilla-daemon
2011-06-16 14:00 ` Avi Kivity [this message]
2011-06-15 21:46 ` bugzilla-daemon
2011-06-16 14:00 ` bugzilla-daemon
2011-06-16 14:15 ` bugzilla-daemon
2011-06-16 16:45 ` bugzilla-daemon
2011-06-16 20:39 ` bugzilla-daemon
2011-06-17 2:25 ` Xiao Guangrong
2011-06-19 8:50 ` Avi Kivity
2011-06-17 3:49 ` bugzilla-daemon
2011-06-17 7:00 ` bugzilla-daemon
2011-06-19 8:50 ` bugzilla-daemon
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=4DFA0C71.1020909@redhat.com \
--to=avi@redhat.com \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=xiaoguangrong@cn.fujitsu.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.