From: Tim Deegan <tim@xen.org>
To: Daniel Castro <evil.dani@gmail.com>, g@phlegethon.org
Cc: xen-devel@lists.xensource.com
Subject: Re: hvm crash on hypercall event channel
Date: Tue, 10 Apr 2012 13:13:44 +0100 [thread overview]
Message-ID: <20120410121344.GA1955@ocelot.phlegethon.org> (raw)
In-Reply-To: <CAP2B85-gvjJ4qbP2Lyz6qEtOb2Gzs6F_EMVHkD5K73KeFHJV1A@mail.gmail.com>
At 20:30 +0900 on 10 Apr (1334089815), Daniel Castro wrote:
> Hello All,
>
> I am writing the PV-Drivers for Seabios.
>
> When I put a request on the front ring and issue the hypercall to
> notify, the hvm guest crashes.
>
> Here is the dmesg output:
>
> (XEN) realmode.c:116:d10 Failed to emulate insn.
> (XEN) realmode.c:166:d10 Real-mode emulation failed @ f000:00001c4b:
> 0f aa ba b2 00 ec
0F AA is RSM, which is a pretty surprising instruction to find in a
hypercall invocation -- or indeed anywhere outside machine-specific SMM
code. Is there SMM code in SeaBIOS? It may be that you've ended up
jumping to a misaligned instruction boundary.
> Nothing out of the ordinary. Except that the hypercall is issued under
> 16bit, It works under 32bit.
Are you using the hypercall page to make your hypercall? Its contents
don't make sense in 16-bit mode, only in 32-bit and 64-bit. Since the
register arguments are 32-bit anyway you might want to make all your
hypercalls from 32-bit code anyway; otherwise you'll need to make your
own 16-bit stubs, with the right prefixes for the MOV imm32.
Cheers,
Tim.
next prev parent reply other threads:[~2012-04-10 12:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-10 11:30 hvm crash on hypercall event channel Daniel Castro
2012-04-10 12:09 ` Keir Fraser
2012-04-10 12:13 ` Tim Deegan [this message]
2012-04-11 12:02 ` Daniel Castro
2012-04-11 12:06 ` Ian Campbell
2012-04-11 12:24 ` Daniel Castro
2012-04-11 12:44 ` Keir Fraser
2012-04-12 7:22 ` Daniel Castro
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=20120410121344.GA1955@ocelot.phlegethon.org \
--to=tim@xen.org \
--cc=evil.dani@gmail.com \
--cc=g@phlegethon.org \
--cc=xen-devel@lists.xensource.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;
as well as URLs for NNTP newsgroup(s).