From: Jan Kiszka <jan.kiszka@web.de>
To: Bug 657329 <657329@bugs.launchpad.net>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [Bug 657329] [NEW] APIC unusable on QEMU
Date: Sat, 09 Oct 2010 16:44:06 +0200 [thread overview]
Message-ID: <4CB07FB6.6070102@web.de> (raw)
In-Reply-To: <20101009135148.4804.78327.malonedeb@palladium.canonical.com>
[-- Attachment #1: Type: text/plain, Size: 1165 bytes --]
Am 09.10.2010 15:51, Geoffrey Lee wrote:
> Public bug reported:
>
> The APIC is unusable with QEMU using x86-64 system emulation. Problem
> exists in the latest stable QEMU 0.12.5 as well as the latest git head.
> I am using Mac OS X 10.6, 64-bit version of QEMU.
>
> The QEMU binary was configured with:
>
> ./configure --target-list=i386-softmmu,x86_64-softmmubck-i-search:
> conf_
>
> Problem is that the hw/apic.c file (as well as a few other naughty
> files) rely on the cpu_single_env global - which is set to NULL in cpu-
> exec.c.
>
> Below is a test reading the local APIC version register:
>
> Before taking it out:
>
> (qemu) xp 0xfee00030
> 00000000fee00030: 0x00000000
> (qemu)
>
> After:
>
> (qemu) xp 0xfee00030
> 00000000fee00030: 0x00050011
> (qemu)
Well, the APIC is very well usable for the VCPUs (which run with proper
cpu_single_env set. It is just out of reach for your debugging attempt.
We are working (granted: not actively ATM) on a proper device dump
interface that will allow to inspect the current APIC state as well.
BTW, your "fix" won't work if you enable io-thread support.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 259 bytes --]
next prev parent reply other threads:[~2010-10-09 14:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-09 13:51 [Qemu-devel] [Bug 657329] [NEW] APIC unusable on QEMU Geoffrey Lee
2010-10-09 14:44 ` Jan Kiszka [this message]
2018-04-10 8:50 ` [Qemu-devel] [Bug 657329] " Thomas Huth
2018-06-10 4:17 ` Launchpad Bug Tracker
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=4CB07FB6.6070102@web.de \
--to=jan.kiszka@web.de \
--cc=657329@bugs.launchpad.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).