From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1KXhYV-0005Qq-MT
	for qemu-devel@nongnu.org; Mon, 25 Aug 2008 15:16:47 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1KXhYT-0005Ne-KY
	for qemu-devel@nongnu.org; Mon, 25 Aug 2008 15:16:46 -0400
Received: from [199.232.76.173] (port=32920 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1KXhYT-0005NL-Ba
	for qemu-devel@nongnu.org; Mon, 25 Aug 2008 15:16:45 -0400
Received: from mail.gmx.net ([213.165.64.20]:59630)
	by monty-python.gnu.org with smtp (Exim 4.60)
	(envelope-from <herbszt@gmx.de>) id 1KXhYS-0007LG-QQ
	for qemu-devel@nongnu.org; Mon, 25 Aug 2008 15:16:45 -0400
Message-ID: <023801c906e7$100ab900$0201a8c0@zeug>
From: "Sebastian Herbszt" <herbszt@gmx.de>
References: <20080825095800.18703.30602.stgit@gleb-debian.qumranet.com.qumranet.com>
	<20080825095830.18703.14942.stgit@gleb-debian.qumranet.com.qumranet.com>
Date: Mon, 25 Aug 2008 21:15:51 +0200
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="UTF-8"; reply-type=original
Content-Transfer-Encoding: 7bit
Subject: [Qemu-devel] Re: [PATCH v2 6/6] Pass cpu speed into SM BIOS.
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org

Gleb Natapov wrote:

<snip>
> +#define CPUFREQ_PREFIX "/sys/devices/system/cpu"
<snip>>
> + f = fopen("/proc/cpuinfo", "r");
<snip>

How stable are the values provided by those files?
AFAIK the data from /proc/cpuinfo does change if cpufreq is used.
Could this somehow "hurt" the VM, e.g. by SMBIOS table value
possibly changing on consecutive qemu starts?

- Sebastian