From: "Simon Holm Thøgersen" <odie@cs.aau.dk>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: lguest@ozlabs.org, virtualization@lists.osdl.org,
Matias Zabaljauregui <zabaljaureguiatgmail.com@ozlabs.org>,
Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [Lguest] [PATCH 4/5] lguest: use KVM hypercalls
Date: Thu, 02 Apr 2009 23:55:24 +0200 [thread overview]
Message-ID: <1238709324.5823.8.camel@odie.local> (raw)
In-Reply-To: <200903271022.38244.rusty@rustcorp.com.au>
fre, 27 03 2009 kl. 10:22 +1030, skrev Rusty Russell:
> From: Matias Zabaljauregui <zabaljauregui@gmail.com>
>
> Impact: cleanup
>
> This patch allow us to use KVM hypercalls
Something has broken in relation to this change. I'm not sure it is this
change itself or one following, but I get the following error when using
lguest:
lguest: unhandled trap 6 at 0x418726 (0x0)
> +static bool is_hypercall(struct lg_cpu *cpu)
> +{
> + u8 insn[3];
> +
> + /* This must be the Guest kernel trying to do something.
> + * The bottom two bits of the CS segment register are the privilege
> + * level. */
> + if ((cpu->regs->cs & 3) != GUEST_PL)
> + return false;
> +
> + /* Is it a vmcall? */
> + __lgread(cpu, insn, guest_pa(cpu, cpu->regs->eip), sizeof(insn));
I've put a printk for insn here that shows up twice. The first time insn
holds the values below, and the second time it holds the values that are
patched in by rewrite_hypercall.
> + return insn[0] == 0x0f && insn[1] == 0x01 && insn[2] == 0xc1;
> +}
I'll investigate further tomorrow, unless someone is already on top of
this. My kernel is 2.6.29-07100-g833bb30 btw.
Simon Holm Thøgersen
next parent reply other threads:[~2009-04-02 22:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200903271022.38244.rusty@rustcorp.com.au>
2009-04-02 21:55 ` Simon Holm Thøgersen [this message]
2009-04-02 23:37 ` Matias Zabaljauregui
2009-04-03 9:28 ` Simon Holm Thøgersen
2009-04-05 13:04 ` Rusty Russell
2009-04-06 6:56 ` Simon Holm Thøgersen
2009-04-08 16:24 ` Patrick McHardy
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=1238709324.5823.8.camel@odie.local \
--to=odie@cs.aau.dk \
--cc=lguest@ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rusty@rustcorp.com.au \
--cc=virtualization@lists.osdl.org \
--cc=zabaljaureguiatgmail.com@ozlabs.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
Powered by JetHome