From: Alexander Graf <agraf@suse.de>
To: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>, qemu-ppc@nongnu.org
Cc: programmingkidx@gmail.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/2] PPC: Cuda: Use cuda timer to expose tbfreq to guest
Date: Mon, 14 Jul 2014 19:21:56 +0200 [thread overview]
Message-ID: <53C411B4.30401@suse.de> (raw)
In-Reply-To: <53C3E35E.1080408@ilande.co.uk>
On 14.07.14 16:04, Mark Cave-Ayland wrote:
> On 13/07/14 21:36, Alexander Graf wrote:
>
>> Mac OS X calibrates a number of frequencies on bootup based on reading
>> tb values on bootup and comparing them to via cuda timer values.
>>
>> The only variable we can really steer well (thanks to KVM) is the cuda
>> frequency. So let's use that one to fake Mac OS X into believing the
>> bus frequency is tbfreq * 4. That way Mac OS X will automatically
>> calculate the correct timebase frequency.
>>
>> With this patch and the patch set I posted earlier I can successfully
>> run Mac OS X 10.2, 10.3 and 10.4 guests with -M mac99 on TCG and KVM.
>
> Fantastic! I thought you mentioned before that there was a problem
> with the way in which OS X used the MMU which meant it wouldn't be
> possible to run under KVM but I guess that has been fixed now?
Yes, a patch for that is on the KVM mailing list. I just relocate the
instruction pointer "somewhere safe" when in split real mode. Very crude
hack, but it works astonishingly well.
> Also do any of these changes help any of the *BSDs to boot further?
I don't know :). I've never tried to boot *BSD on PPC, so I have no idea
where that's broken.
Alex
prev parent reply other threads:[~2014-07-14 17:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-13 20:36 [Qemu-devel] [PATCH 1/2] PPC: Mac: Move tbfreq into local variable Alexander Graf
2014-07-13 20:36 ` [Qemu-devel] [PATCH 2/2] PPC: Cuda: Use cuda timer to expose tbfreq to guest Alexander Graf
2014-07-14 14:04 ` Mark Cave-Ayland
2014-07-14 17:21 ` Alexander Graf [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=53C411B4.30401@suse.de \
--to=agraf@suse.de \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=programmingkidx@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.