From: "Mulyadi Santosa" <mulyadi.santosa@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] FreeBSD/amd64 guests with -kernel-kqemu, pagefault at mov %r10d, %gs
Date: Wed, 7 May 2008 10:05:13 +0700 [thread overview]
Message-ID: <f284c33d0805062005w1b66405w6485d85a06bfd084@mail.gmail.com> (raw)
In-Reply-To: <20080506185911.GA23589@saturn.kn-bremen.de>
Hi...
On Wed, May 7, 2008 at 1:59 AM, Juergen Lock <nox@jelal.kn-bremen.de> wrote:
> ..before that it does a mov %r10d,%fs which seems to work (%r10d is
> _udatasel in both cases) so it can't be the segment itself that it
> doesn't like, or can it? Anyone have an idea what this might be?
> (it works without -kernel-kqemu.)
<..snip..>
> 0xffffffff806dc752 <exec_setregs+98>: mov 4183943(%rip),%r10d # 0xffffffff80ad9ee0 <_udatasel>
> 0xffffffff806dc759 <exec_setregs+105>: mov %r10d,%ds
> 0xffffffff806dc75c <exec_setregs+108>: mov %r10d,%es
> 0xffffffff806dc75f <exec_setregs+111>: mov %ebx,%ecx
> 0xffffffff806dc761 <exec_setregs+113>: rdmsr
> 0xffffffff806dc763 <exec_setregs+115>: mov %r10d,%fs
> 0xffffffff806dc766 <exec_setregs+118>: wrmsr
> 0xffffffff806dc768 <exec_setregs+120>: mov $0xc0000101,%ecx
> 0xffffffff806dc76d <exec_setregs+125>: pushfq
> 0xffffffff806dc76e <exec_setregs+126>: cli
> 0xffffffff806dc76f <exec_setregs+127>: rdmsr
> 0xffffffff806dc771 <exec_setregs+129>: mov %r10d,%gs
> failed insn ^^^^^^^^^^^^^^^^^^
I think I agree somehow accessing %gs is the quirk. let's just hope gs
points to valid entry in GDT or LDT...
But may I ask, what does the effect of "cli" in -kernel-kqemu on
FreeBSD's kqemu?
regards,
Mulyadi.
next prev parent reply other threads:[~2008-05-07 3:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-06 18:59 [Qemu-devel] FreeBSD/amd64 guests with -kernel-kqemu, pagefault at mov %r10d, %gs Juergen Lock
2008-05-07 3:05 ` Mulyadi Santosa [this message]
2008-05-09 21:20 ` Juergen Lock
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=f284c33d0805062005w1b66405w6485d85a06bfd084@mail.gmail.com \
--to=mulyadi.santosa@gmail.com \
--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).