From: Anand Kumria <wildfire@progsoc.org>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] two CPU structs in vl.c
Date: Tue, 09 Nov 2004 12:13:49 +1100 [thread overview]
Message-ID: <pan.2004.11.08.23.52.45.447169@progsoc.org> (raw)
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!
reply other threads:[~2004-11-09 1:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=pan.2004.11.08.23.52.45.447169@progsoc.org \
--to=wildfire@progsoc.org \
--cc=qemu-devel@nongnu.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).