From: Kevin O'Connor <kevin@koconnor.net>
To: Aurelien Jarno <aurelien@aurel32.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] call insn not truncated on x86_64
Date: Sat, 2 Jan 2010 17:28:28 -0500 [thread overview]
Message-ID: <20100102222828.GA31624@morn.localdomain> (raw)
In-Reply-To: <20100102203538.GB5837@hall.aurel32.net>
On Sat, Jan 02, 2010 at 09:35:38PM +0100, Aurelien Jarno wrote:
> On Sat, Jan 02, 2010 at 01:26:54PM -0500, Kevin O'Connor wrote:
> > I'm running into an issue with SeaBIOS compiled with older versions of
> > gcc. I'm seeing:
> >
> > $ qemu-system-x86_64 -d in_asm,int,exec,cpu,pcall
> >
> > IN:
> > 0x00000000000f1096: mov %ebx,%eax
> > 0x00000000000f1098: call 0xffff0f80
> >
> > qemu: fatal: Trying to execute code outside RAM or ROM at 0xffffffffffff0f80
>
> The problem has been fixed in 32938e127f50a40844a0fb9c5abb8691aeeccf7e
> for jmp imm. I guess the same patch applies for call. Could you confirm?
Your patch fixes the problem.
Thanks,
-Kevin
prev parent reply other threads:[~2010-01-02 22:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-02 18:26 [Qemu-devel] call insn not truncated on x86_64 Kevin O'Connor
2010-01-02 20:35 ` Aurelien Jarno
2010-01-02 22:28 ` Kevin O'Connor [this message]
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=20100102222828.GA31624@morn.localdomain \
--to=kevin@koconnor.net \
--cc=aurelien@aurel32.net \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).