From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>,
Aaron Elkins <threcius@yahoo.com>
Cc: "qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Qemu: Guest Linux hangs on Mac OS X 10.11
Date: Mon, 9 Nov 2015 10:10:45 +0100 [thread overview]
Message-ID: <56406315.6050402@redhat.com> (raw)
In-Reply-To: <CAFEAcA-z=qVNi7f-REAcTtA5nF5Ps78us7mVOnucCTi1=7K-Lg@mail.gmail.com>
On 08/11/2015 23:55, Peter Maydell wrote:
> So the good news is that on mainline this doesn't happen any more.
> The bad news is that something weird is going on such that git
> bisect doesn't give helpful answers. Specifically if I start by
> compiling older versions and work forwards, then
> 0fd7e09 kvmclock: add a new function to update env->tsc.
> shows the bug, and
> 6388acc Revert "Introduce cpu_clean_all_dirty"
> does not. (And I've got to that commit both via a git-bisect
> and by a second round of manually trying to identify the commit,
> so it's consistent about where it changes behaviour.)
> However that makes no sense because that revert commit
> is just removing unused code. And then if I go backwards again
> to 0fd7e09 the bug doesn't repro there.
Even 0fd7e09 does not change behavior unless you use KVM (which you
obviously don't do under Mac OS X). So if you go backwards to 0fd7e09^
it shouldn't reproduce there either.
What is the known bad SHA1?
Paolo
next prev parent reply other threads:[~2015-11-09 9:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-16 7:32 [Qemu-devel] Qemu: Guest Linux hangs on Mac OS X 10.11 Aaron Elkins
2015-10-18 19:46 ` Peter Maydell
2015-10-18 20:37 ` Peter Maydell
2015-10-19 5:09 ` Aaron Elkins
2015-10-19 5:50 ` Aaron Elkins
2015-11-08 22:55 ` Peter Maydell
2015-11-09 9:10 ` Paolo Bonzini [this message]
2015-11-09 10:02 ` Peter Maydell
2015-11-09 10:21 ` Paolo Bonzini
2015-11-09 11:06 ` Peter Maydell
2015-11-09 11:46 ` Peter Maydell
2015-11-09 13:30 ` Peter Maydell
2015-11-09 13:40 ` Paolo Bonzini
2015-11-09 14:26 ` Peter Maydell
2015-11-09 16:59 ` Peter Maydell
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=56406315.6050402@redhat.com \
--to=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=threcius@yahoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).