From: "andrey mirtchovski" <mirtchovski@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] Support for Mac OS X Leopard
Date: Sat, 29 Sep 2007 15:49:51 -0600 [thread overview]
Message-ID: <14ec7b180709291449g3ca45fd9k6d8f2609e87e2597@mail.gmail.com> (raw)
In-Reply-To: <8ccc8ba40709291430r6c2b8327g2c34ed37fee4cf5b@mail.gmail.com>
On 9/29/07, Francisco J Ballesteros <nemo@lsub.org> wrote:
> I´m using both a macbook pro and a macbook regularly.
> Plan9 on Parallels works fine, although time does funny things when
> you suspend (I do not) and some times parallels crashes (not plan 9) when
> you start it.
>
if you don't mind your parallels p9 to run with the wrong time you can
simply stop timesync and you'll have no issues with suspend/restart.
the problem is that when timesync puts the new time in after a suspend
the system recalculated the cpu clock rate and forces it down the
cpu's throat, which causes time to run much faster than usual.
here's a snippet from a discussion we had with jmk trying to figure
this one out a few months ago:
> devcons.c:^writebintime forces a new clock frequency down the kernel's
> throat at the writer's behest. the writer in this case is timesync...
> perhaps it shouldn't be allowed to do so?
i don't know a solution, i simply avoid running timesync under parallels
next prev parent reply other threads:[~2007-09-29 21:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-29 19:52 Tharaneedharan Vilwanathan
2007-09-29 19:57 ` andrey mirtchovski
2007-09-29 20:25 ` Tharaneedharan Vilwanathan
2007-09-29 21:30 ` Francisco J Ballesteros
2007-09-29 21:49 ` andrey mirtchovski [this message]
2007-09-29 21:50 ` andrey mirtchovski
2007-09-30 15:18 ` Jack Johnson
2007-09-30 18:20 ` Russ Cox
2007-09-30 18:27 ` andrey mirtchovski
2007-09-30 21:09 ` Russ Cox
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=14ec7b180709291449g3ca45fd9k6d8f2609e87e2597@mail.gmail.com \
--to=mirtchovski@gmail.com \
--cc=9fans@cse.psu.edu \
/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).