From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: "Zhao, Yunfeng" <yunfeng.zhao-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: ABAT Testing report, kernel 3415130f97.., user a125fbfd0..
Date: Sat, 04 Aug 2007 13:09:15 +0300 [thread overview]
Message-ID: <46B4504B.2060308@qumranet.com> (raw)
In-Reply-To: <10EA09EFD8728347A513008B6B0DA77AA3EFAE-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
Zhao, Yunfeng wrote:
> Avi,
> Thank you very much for the fix!
> I will try to update to new kernel in our testing.
>
The build fix is in kvm-userspace.git.
> For the crash issue, do you mean this issue only happens on old kernel?
>
>
Yes. It should not happen if the kernel is compiled from kvm.git, only
if compiled as an external module.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
next prev parent reply other threads:[~2007-08-04 10:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-03 8:00 ABAT Testing report, kernel 3415130f97.., user a125fbfd0 Zhao, Yunfeng
[not found] ` <10EA09EFD8728347A513008B6B0DA77A01E0079D-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-08-03 16:14 ` Avi Kivity
[not found] ` <46B35458.5090502-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-08-04 3:29 ` Zhao, Yunfeng
[not found] ` <10EA09EFD8728347A513008B6B0DA77AA3EFAE-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-08-04 10:09 ` Avi Kivity [this message]
[not found] ` <46B4504B.2060308-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-08-04 10:28 ` Zhao, Yunfeng
2007-08-05 11:18 ` 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=46B4504B.2060308@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=yunfeng.zhao-ral2JQCrhuEAvxtiuMwx3w@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