From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: "Yang, Sheng" <sheng.yang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Test result for KVM
Date: Sun, 30 Sep 2007 11:50:45 +0200 [thread overview]
Message-ID: <46FF7175.1080109@qumranet.com> (raw)
In-Reply-To: <DB3BD37E3533EE46BED2FBA80995557F8C808C-wq7ZOvIWXbM/UvCtAeCM4rfspsVTdybXVpNB7YpNyf8@public.gmane.org>
Yang, Sheng wrote:
>> 1. 64bit guest with 2.6.16 kernel crashes when start up nic
>>
>
> https://sourceforge.net/tracker/index.php?func=detail&aid=1804658&group_
> id=180599&atid=893831
>
> I found this is a instruction emulate problem. Guest try to execute
> "movnti", but we haven't got it yet...
>
> Nitin, can you help to solve it?
>
In general we should recover from emulation failures caused by writes to
page tables, but not for mmio.
Was the instruction executed for mmio or a page table update?
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
next prev parent reply other threads:[~2007-09-30 9:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-30 7:08 Test result for KVM Zhao, Yunfeng
[not found] ` <10EA09EFD8728347A513008B6B0DA77A02125F40-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-09-30 7:54 ` Zhao, Yunfeng
2007-09-30 9:40 ` Yang, Sheng
[not found] ` <DB3BD37E3533EE46BED2FBA80995557F8C808C-wq7ZOvIWXbM/UvCtAeCM4rfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-09-30 9:50 ` Avi Kivity [this message]
[not found] ` <46FF7175.1080109-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-09-30 9:59 ` Yang, Sheng
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=46FF7175.1080109@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=sheng.yang-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