From: "nicolas.sauzede" <nicolas.sauzede@laposte.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Get current env within io_handler ?
Date: Tue, 15 May 2012 17:12:46 +0200 [thread overview]
Message-ID: <1512121653.606644.1337094765947.JavaMail.www@wwinf8306> (raw)
[-- Attachment #1: Type: text/plain, Size: 1041 bytes --]
Hi list,
I've implemented a way to link a qemu instance (arm) to a running TLM simulation.
That allows me to use qemu-system-arm as a minimal ARM ISS without any hardware device implemented within qemu,
all the peripherals are implemented in the TLM simulation.
This works by entering the TLM world when called back in the io_handlers.
This works fine for uniprocessor mode.
But when trying smp mode, I can't manage to retrieve the current env (ie: current smp processor number, registers, etc..),
because it seems like the "cpu_single_env" variable is set to NULL explicitly in cpu-exec.c :
/* fail safe : never use cpu_single_env outside cpu_exec() */
cpu_single_env = NULL;
return ret;
}
Is this intentional ? Would it be very bad to get access to the current env in io_handler ? (it works if commenting out "cpu_single_env = NULL;")
Thanks by advance,
NS.
Une messagerie gratuite, garantie à vie et des services en plus, ça vous tente ?
Je crée ma boîte mail www.laposte.net
[-- Attachment #2: Type: text/html, Size: 1108 bytes --]
next reply other threads:[~2012-05-15 15:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-15 15:12 nicolas.sauzede [this message]
2012-05-15 15:19 ` [Qemu-devel] Get current env within io_handler ? Andreas Färber
2012-05-15 15:31 ` nicolas.sauzede
2012-05-15 16:33 ` Peter Maydell
2012-05-15 16:34 ` Andreas Färber
2012-05-16 7:58 ` nicolas.sauzede
2012-05-19 7:13 ` Blue Swirl
2012-05-19 9:39 ` Peter Maydell
2012-05-21 7:21 ` nicolas.sauzede
2012-05-21 10:36 ` Peter Maydell
2012-05-21 18:08 ` Blue Swirl
2012-05-21 18:28 ` Peter Maydell
2012-05-21 18:40 ` Blue Swirl
2012-05-21 22:06 ` Edgar E. Iglesias
2012-05-21 11:57 ` Andreas Färber
2012-05-15 16:34 ` Anthony Liguori
2012-05-16 7:56 ` nicolas.sauzede
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=1512121653.606644.1337094765947.JavaMail.www@wwinf8306 \
--to=nicolas.sauzede@laposte.net \
--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).