From: Rusty Russell <rusty@rustcorp.com.au>
To: Matt Mackall <mpm@selenic.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
virtualization <virtualization@lists.linux-foundation.org>
Subject: Re: [PATCH 1/2] lguest: handle dodgy/non-existent TSC. Host code.
Date: Thu, 05 Jul 2007 11:38:45 +1000 [thread overview]
Message-ID: <1183599525.6005.55.camel@localhost.localdomain> (raw)
In-Reply-To: <20070704132025.GZ11115@waste.org>
On Wed, 2007-07-04 at 08:20 -0500, Matt Mackall wrote:
> On Wed, Jul 04, 2007 at 04:19:32PM +1000, Rusty Russell wrote:
> > Lguest currently requires a TSC, which breaks older machines and Matt
> > Mackall who boots the host with "notsc".
>
> I do? I temporarily had a "notsc" arg in my lguest launcher script,
> but removing it made no difference. I do* boot the host with NO_HZ though.
NO_HZ should be OK, but last we spoke, "notsc" in the host caused
lguest_data.tsc_khz to be zero => divide by zero errors (the previous
fixes should sort out the other TSC issues).
Anyway, if the host decides not to use the TSC, the guest shouldn't use
it, which is the basis of this patch...
Hope that clarifies,
Rusty.
next prev parent reply other threads:[~2007-07-05 1:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-04 6:19 [PATCH 1/2] lguest: handle dodgy/non-existent TSC. Host code Rusty Russell
2007-07-04 6:20 ` [PATCH 2/2] lguest: handle dodgy/non-existent TSC. Guest code Rusty Russell
2007-07-04 6:44 ` Tony Breeds
2007-07-04 8:10 ` Rusty Russell
2007-07-05 15:37 ` john stultz
2007-07-05 17:56 ` Jeremy Fitzhardinge
2007-07-04 13:20 ` [PATCH 1/2] lguest: handle dodgy/non-existent TSC. Host code Matt Mackall
2007-07-05 1:38 ` Rusty Russell [this message]
2007-07-05 6:41 ` Matt Mackall
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=1183599525.6005.55.camel@localhost.localdomain \
--to=rusty@rustcorp.com.au \
--cc=akpm@linux-foundation.org \
--cc=mpm@selenic.com \
--cc=virtualization@lists.linux-foundation.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).