From: Paolo Bonzini <pbonzini@redhat.com>
To: "Hu, Robert" <robert.hu@intel.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: KVM Test report, kernel fd275235... qemu e4d50d47...
Date: Thu, 18 Sep 2014 11:25:30 +0200 [thread overview]
Message-ID: <541AA50A.5040001@redhat.com> (raw)
In-Reply-To: <9E79D1C9A97CFD4097BCE431828FDD31A0785F@SHSMSX103.ccr.corp.intel.com>
Il 18/09/2014 10:23, Hu, Robert ha scritto:
> Hi All,
>
> This is KVM upstream test result against kvm.git next branch and qemu.git master branch.
> kvm.git next branch: fd2752352bbc98850d83b5448a288d8991590317 based on kernel 3.17.0-rc1
> qemu.git master branch: e4d50d47a9eb15f42bdd561803a29a4d7c3eb8ec
>
> We found one new bug and no fix bugs in the past three weeks.
Thanks.
> New issue (1):
> 1. The guest will hang after live migration.
> https://bugzilla.kernel.org/show_bug.cgi?id=84781
> the first bad commit is:
> commit cbcf2dd3b3d4d990610259e8d878fc8dc1f17d80
> Author: Thomas Gleixner <tglx@linutronix.de>
> Date: Wed Jul 16 21:04:54 2014 +0000
>
> x86: kvm: Make kvm_get_time_and_clockread() nanoseconds based
>
> Convert the relevant base data right away to nanoseconds instead of
> doing the conversion on every readout. Reduces text size by 160 bytes.
>
> Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
> Cc: Gleb Natapov <gleb@kernel.org>
> Cc: kvm@vger.kernel.org
> Acked-by: Paolo Bonzini <pbonzini@redhat.com>
> Signed-off-by: John Stultz <john.stultz@linaro.org>
This should be fixed by 3.17-rc4. Please test Linus tree.
Paolo
next prev parent reply other threads:[~2014-09-18 9:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8F9B1D95D29E8A42905D3F4AAB23ED140A71F293@SHSMSX103.ccr.corp.intel.com>
2014-09-18 8:23 ` KVM Test report, kernel fd275235... qemu e4d50d47 Hu, Robert
2014-09-18 9:25 ` Paolo Bonzini [this message]
2014-09-19 5:36 ` Hu, Robert
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=541AA50A.5040001@redhat.com \
--to=pbonzini@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=robert.hu@intel.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