From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33)
	id 1CRKei-0006Z0-3s
	for qemu-devel@nongnu.org; Mon, 08 Nov 2004 20:18:44 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33)
	id 1CRKeh-0006Yk-JQ
	for qemu-devel@nongnu.org; Mon, 08 Nov 2004 20:18:43 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.33) id 1CRKeh-0006Ya-Fl
	for qemu-devel@nongnu.org; Mon, 08 Nov 2004 20:18:43 -0500
Received: from [80.91.229.2] (helo=main.gmane.org)
	by monty-python.gnu.org with esmtp (Exim 4.34) id 1CRKVz-0002pZ-Nt
	for qemu-devel@nongnu.org; Mon, 08 Nov 2004 20:09:43 -0500
Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian))
	id 1CRKVy-0007lF-00
	for <qemu-devel@nongnu.org>; Tue, 09 Nov 2004 02:09:42 +0100
Received: from adsl-60-232.swiftdsl.com.au ([218.214.60.232])
	by main.gmane.org with esmtp (Gmexim 0.1 (Debian))
	id 1AlnuQ-0007hv-00
	for <qemu-devel@nongnu.org>; Tue, 09 Nov 2004 02:09:42 +0100
Received: from wildfire by adsl-60-232.swiftdsl.com.au with local (Gmexim 0.1
	(Debian)) id 1AlnuQ-0007hv-00
	for <qemu-devel@nongnu.org>; Tue, 09 Nov 2004 02:09:42 +0100
From: Anand Kumria <wildfire@progsoc.org>
Date: Tue, 09 Nov 2004 12:13:49 +1100
Message-ID: <pan.2004.11.08.23.52.45.447169@progsoc.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Sender: news <news@sea.gmane.org>
Subject: [Qemu-devel] two CPU structs in vl.c
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


Hi,

Just wondering why there are both:

CPUState *global_env;
CPUState *cpu_single_env;

why do you need both?

Thanks,
Anand

-- 
linux.conf.au 2005   -  http://lca2005.linux.org.au/  -  Birthplace of Tux
April 18th to 23rd   -  http://lca2005.linux.org.au/  -       LINUX
Canberra, Australia  -  http://lca2005.linux.org.au/  -    Get bitten!