qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Gabriel L. Somlo" <gsomlo@gmail.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	seabios@seabios.org, kraxel@redhat.com, qemu-devel@nongnu.org,
	agraf@suse.de
Subject: Re: [Qemu-devel] os x boot broken by commit 11948748495841bd54721b250d68c7b3cb0475ef
Date: Tue, 26 Nov 2013 12:06:09 +0200	[thread overview]
Message-ID: <20131126100609.GA19371@redhat.com> (raw)
In-Reply-To: <20131121220207.GO13775@HEDWIG.INI.CMU.EDU>

On Thu, Nov 21, 2013 at 05:02:07PM -0500, Gabriel L. Somlo wrote:
> Added qemu-devel, since that is where this stuff belongs now. Everyone
> else, sorry for the dupe...
> 
> On Thu, Nov 21, 2013 at 07:14:27PM +0100, Paolo Bonzini wrote:
> > Can you remind us about your DSDT modifications?  It should be possible
> > to patch the HPET and applesmc bits appropriately from QEMU (or to move
> > them from the DSDT to an SSDT that is built entirely in QEMU).
> > 
> > It actually isn't impossible that Mac OS X would boot just fine with 1.8...
> 
> My current DSDT patch (against QEMU) is enclosed below. The HPET
> basically needs "IRQNoFlags() {2, 8}", which causes XP to bluescreen.
> 
> So, I've made it conditional on the SMC STA method returning success
> (0x0B).
> 
> The SMC node's STA method returns 0x0B unconditionally on real
> hardware. So I was planning on figuring out what's easier in the
> context of the most recent QEMU code base:
> 
> 	1. dynamically generating (during qemu runtime initialization)
> 	 a DSDT entry for SMC with hardcoded 0x0B STA method, whenever
> 	"--device isa-applesmc" is present on the qemu command line
> 
> or
> 
> 	2. writing a static (compile-time) SMC node but with a slightly
> 	smarter _STA method, which returns 0x0B when "--device isa-applesmc"
> 	was given on the cmdline, or which returns 0x00 in the absence
> 	of "--device isa-applesmc".
> 
> Either 1. or 2. could be used with HPET -- I can make inclusion of
> IRQNoFlags dependent on either the success or on the presence of
> SMC._STA() :)
> 
> Let me know what you think.
> 
> Thanks,
> --Gabriel

Without discussing whether this is the right thing to do,
main options to implement this would be:

        - write code in ASL, supply entry in ACPI always, patch some
          fields
          to enable/disable it dynamically

        see how pvpanic entry is disabled for an example

        - write code in ASL append it to ACPI if necessary

        see how CPU entries are added depending on number of CPUs for an example

        - generate code in AML directly

        see acpi based pci hotplug on pci branch in my tree for an example

      parent reply	other threads:[~2013-11-26 10:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20131111213933.GG13775@HEDWIG.INI.CMU.EDU>
     [not found] ` <20131111221821.GH13775@HEDWIG.INI.CMU.EDU>
     [not found]   ` <528E4D83.6070708@redhat.com>
2013-11-21 22:02     ` [Qemu-devel] os x boot broken by commit 11948748495841bd54721b250d68c7b3cb0475ef Gabriel L. Somlo
2013-11-22  9:00       ` Paolo Bonzini
2013-11-26 10:16         ` Michael S. Tsirkin
2013-11-26 10:06       ` Michael S. Tsirkin [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=20131126100609.GA19371@redhat.com \
    --to=mst@redhat.com \
    --cc=agraf@suse.de \
    --cc=gsomlo@gmail.com \
    --cc=kraxel@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=seabios@seabios.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).