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
