From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([208.118.235.92]:54013)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <anthony@codemonkey.ws>) id 1SUKi3-0002Ch-Eo
	for qemu-devel@nongnu.org; Tue, 15 May 2012 12:34:57 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <anthony@codemonkey.ws>) id 1SUKi1-0001RT-Mb
	for qemu-devel@nongnu.org; Tue, 15 May 2012 12:34:51 -0400
Received: from mail-yw0-f46.google.com ([209.85.213.46]:51771)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <anthony@codemonkey.ws>) id 1SUKi1-0001RK-Id
	for qemu-devel@nongnu.org; Tue, 15 May 2012 12:34:49 -0400
Received: by yhmm54 with SMTP id m54so7135388yhm.33
	for <qemu-devel@nongnu.org>; Tue, 15 May 2012 09:34:48 -0700 (PDT)
Message-ID: <4FB285A5.6030205@codemonkey.ws>
Date: Tue, 15 May 2012 11:34:45 -0500
From: Anthony Liguori <anthony@codemonkey.ws>
MIME-Version: 1.0
References: <1512121653.606644.1337094765947.JavaMail.www@wwinf8306>
	<4FB27400.3010908@suse.de>
	<27874590.608345.1337095907076.JavaMail.www@wwinf8306>
In-Reply-To: <27874590.608345.1337095907076.JavaMail.www@wwinf8306>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] Get current env within io_handler ?
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: "nicolas.sauzede" <nicolas.sauzede@laposte.net>
Cc: =?UTF-8?B?QW5kcmVhcyBGw6RyYmVy?= <afaerber@suse.de>, qemu-devel@nongnu.org

On 05/15/2012 10:31 AM, nicolas.sauzede wrote:
> Sorry,
> What I meant was the IO handlers we can register, when initializing an io memory area :
>
>      iomemtype = cpu_register_io_memory(tlm_qemu_readfn,
>                                         tlm_qemu_writefn, s,
>                                         DEVICE_NATIVE_ENDIAN);

Yes, it's entirely intentional to prevent io handlers from accessing CPUState.

For what you're doing, you need to hook more deeply into target-arm before the 
dispatch actually happens.

Regards,

Anthony Liguori