qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Gabriel L. Somlo" <gsomlo@gmail.com>
To: qemu-devel@nongnu.org
Cc: rene@exactcode.com, jan.kiszka@siemens.com, jbaron@redhat.com,
	agraf@suse.de, kraxel@redhat.com, anthony@codemonkey.ws
Subject: Re: [Qemu-devel] [PULL for-1.3 0/3] seabios: q35 update
Date: Tue, 4 Dec 2012 09:42:44 -0500	[thread overview]
Message-ID: <20121204144243.GB13356@hedwig.ini.cmu.edu> (raw)
In-Reply-To: <50BDA8EB.5090402@redhat.com>

On Tue, 04 Dec 2012 08:40:27 +0100 Gerd Hoffmann wrote:
>On Mon, 3 Dec 2012 13:47:04 -0500, Jason Baron wrote:
>> 2) HPET ACPI error
>> 
>> This line: 'IRQNoFlags () {2, 8}' in the HPET acpi table is causing the
>> folloing ACPI message (removing it makes it go away):
>
> Hmm.  That was added to make macos x happy and is also present on real
> hardware, so I'm wondering what is going on here.

Without that line, OS X only works as a single-core, non-SMP guest.
This is the "legacy replacement irq mapping" option for HPET (section
2.4.2, page 24 of the IA-PC HPET Specification).

The options are 'IRQNoFlags () {2, 8}' for "APIC mapping" or
'IRQNoFlags () {0, 8}' for "8259 mapping". Either one works for SMP + OS X.

I don't have an XP install image anymore, but does replacing 2,8 with
0,8 help ?

On a few of my machines, this is actually coded as

                        IRQNoFlags ()
                            {0}			/* or 2 */
                        IRQNoFlags ()
                            {8}

Based on my reading of the ACPI manual, this should be syntactically
equivalent to the the comma-separated single-line format we're currently
using, but could it be that WinXP is picky about the specifics ?

Also, as far as I can tell, this change never made it into the
"q35-acpi-dsdt.dsl" file, just the "classic" acpi-dsdt.dsl (or, lately,
acpi-dsdt-hpet.dsl). I was about to submit another patch for that, but
now I guess I won't press it until we sort this out :)

--Gabriel

  parent reply	other threads:[~2012-12-04 14:43 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-03 10:11 [Qemu-devel] [PULL for-1.3 0/3] seabios: q35 update Gerd Hoffmann
2012-12-03 10:11 ` [Qemu-devel] [PATCH 1/3] seabios: update to 3d11108f45818d75140530a184c05680f1be51ad Gerd Hoffmann
2012-12-03 10:11 ` [Qemu-devel] [PATCH 2/3] configure: also symlink *.aml files Gerd Hoffmann
2012-12-03 10:11 ` [Qemu-devel] [PATCH 3/3] acpi: autoload dsdt Gerd Hoffmann
2012-12-03 18:47 ` [Qemu-devel] [PULL for-1.3 0/3] seabios: q35 update Jason Baron
2012-12-04  7:40   ` Gerd Hoffmann
2012-12-04  7:46     ` Jan Kiszka
2012-12-04 14:37     ` Jason Baron
2012-12-04 15:37       ` Gerd Hoffmann
2012-12-04 15:57         ` Gerd Hoffmann
2012-12-04 14:42     ` Gabriel L. Somlo [this message]
2012-12-04 15:11       ` jbaron
2012-12-04 15:39         ` Gabriel L. Somlo
2012-12-04 16:56           ` Gerd Hoffmann
2012-12-04 17:14             ` Gabriel L. Somlo
2012-12-05  6:50               ` Gerd Hoffmann
2012-12-05 14:49                 ` Gabriel L. Somlo

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=20121204144243.GB13356@hedwig.ini.cmu.edu \
    --to=gsomlo@gmail.com \
    --cc=agraf@suse.de \
    --cc=anthony@codemonkey.ws \
    --cc=jan.kiszka@siemens.com \
    --cc=jbaron@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rene@exactcode.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).