[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <47272007.8000108@redhat.com>
Date: Tue, 30 Oct 2007 10:13:59 -0200
From: Glauber de Oliveira Costa <gcosta@...hat.com>
To: Ingo Molnar <mingo@...e.hu>
CC: Rusty Russell <rusty@...tcorp.com.au>,
Thomas Gleixner <tglx@...utronix.de>,
LKML <linux-kernel@...r.kernel.org>,
Jeremy Fitzhardinge <jeremy@...p.org>, --cc@...hat.com,
avi@...amnet.com, kvm-devel@...ts.sourceforge.net,
John Stultz <johnstul@...ibm.com>
Subject: Re: [PATCH] raise tsc clocksource rating
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Ingo Molnar escreveu:
> * Rusty Russell <rusty@...tcorp.com.au> wrote:
>
> and just in case it's not obvious: i am not arguing for the inclusion of
> the patch, i'm just pointing out the plain fact that in the case where
> the TSC _is_ reliable, 5 different clocksource drivers for has obvious
> disadvantages. Anyone arguing against that simple point needs his head
> examined :) Once we can pass around calibration information from the
> host to the guest (which we dont do at the moment) there will be reason
> not to use the native clocksource driver in the guest.
If you sustain that we cannot have a reliable synchronization test
mechanism, neither do I. All this is based in the assumption that a bad
tsc will fail such tests.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Remi - http://enigmail.mozdev.org
iD8DBQFHJyAHjYI8LaFUWXMRAtYoAJ9l5kNodRLfTsNHDvyioufM7SQzTACfarEy
XXq3sDq9uxZ/72hhA46YmgM=
=DwN/
-----END PGP SIGNATURE-----
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists