All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: "nicolas.sauzede" <nicolas.sauzede@laposte.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Get current env within io_handler ?
Date: Tue, 15 May 2012 17:19:28 +0200	[thread overview]
Message-ID: <4FB27400.3010908@suse.de> (raw)
In-Reply-To: <1512121653.606644.1337094765947.JavaMail.www@wwinf8306>

Am 15.05.2012 17:12, schrieb nicolas.sauzede:
> [...] 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;")

I don't understand what io_handler you mean, but usually you have access
to an "env" variable, either passed explicitly or available pinned to
AREG0 register. cpu_single_env by contrary is most likely not the
solution you are looking for.

Andreas

-- 
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

  reply	other threads:[~2012-05-15 15:19 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-15 15:12 [Qemu-devel] Get current env within io_handler ? nicolas.sauzede
2012-05-15 15:19 ` Andreas Färber [this message]
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=4FB27400.3010908@suse.de \
    --to=afaerber@suse.de \
    --cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.