From: Hollis Blanchard <hollisb@us.ibm.com>
To: kvm-ppc@vger.kernel.org
Subject: Re: [kvm-ppc-devel] Guests oops when trying to mount initramfs
Date: Thu, 13 Mar 2008 18:34:53 +0000 [thread overview]
Message-ID: <1205433293.12603.10.camel@basalt> (raw)
In-Reply-To: <47D7C7FF.2060306@linux.vnet.ibm.com>
On Thu, 2008-03-13 at 18:53 +0100, Christian Ehrhardt wrote:
> ok for Hollis to continue and anyone else that might have comments
> -> tracking any eviction of the guest kernel mapping (=0xC..) did not
> trigger
> -> tracking the delivery of a itlb/dtlb miss with that address did not
> trigger
> -> I inserted a BUG statement in the guests report of "Unable to
> handle kernel paging request ..."
> That triggers a emulation of a trap in the host and there I have a
> dump_vcpu&dump_tlb
>
I think this just means our debug tests in the host kernel aren't
working. The *only* way the guest interrupt vectors are invoked is by
the host kernel...
--
Hollis Blanchard
IBM Linux Technology Center
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
kvm-ppc-devel mailing list
kvm-ppc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-ppc-devel
next prev parent reply other threads:[~2008-03-13 18:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-12 12:09 [kvm-ppc-devel] Guests oops when trying to mount initramfs Christian Ehrhardt
2008-03-12 13:35 ` Hollis Blanchard
2008-03-13 17:53 ` Christian Ehrhardt
2008-03-13 18:34 ` Hollis Blanchard [this message]
2008-03-14 12:31 ` Christian Ehrhardt
2008-03-17 15:13 ` Christian Ehrhardt
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=1205433293.12603.10.camel@basalt \
--to=hollisb@us.ibm.com \
--cc=kvm-ppc@vger.kernel.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 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.