All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@citrix.com>
To: Daniel Castro <evil.dani@gmail.com>
Cc: "g@phlegethon.org" <g@phlegethon.org>,
	"Tim (Xen.org)" <tim@xen.org>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: hvm crash on hypercall event channel
Date: Wed, 11 Apr 2012 13:06:29 +0100	[thread overview]
Message-ID: <1334145989.16387.7.camel@zakaz.uk.xensource.com> (raw)
In-Reply-To: <CAP2B859SaKU6YD3=DPuC8ceofz7uHgjodjDfMv5sW5U=xVQgvw@mail.gmail.com>

On Wed, 2012-04-11 at 13:02 +0100, Daniel Castro wrote:
> On Tue, Apr 10, 2012 at 9:13 PM, Tim Deegan <tim@xen.org> wrote:
> > 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.
> 
> I have no idea how to fix this :(

It's looking likely that you'll have to go to 32 bit mode to do all of
the actual I/O associated with the PV devices. That ought to simplify a
bunch of stuff WRT handling the rings etc too.

Ian.

  reply	other threads:[~2012-04-11 12:06 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
2012-04-11 12:02   ` Daniel Castro
2012-04-11 12:06     ` Ian Campbell [this message]
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=1334145989.16387.7.camel@zakaz.uk.xensource.com \
    --to=ian.campbell@citrix.com \
    --cc=evil.dani@gmail.com \
    --cc=g@phlegethon.org \
    --cc=tim@xen.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 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.