From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([208.118.235.92]:49757)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <nicolas.sauzede@laposte.net>) id 1SUZ6V-0007AF-Mp
	for qemu-devel@nongnu.org; Wed, 16 May 2012 03:57:09 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <nicolas.sauzede@laposte.net>) id 1SUZ6P-0004F4-4C
	for qemu-devel@nongnu.org; Wed, 16 May 2012 03:57:03 -0400
Received: from smtpout1.laposte.net ([193.253.67.226]:43270
	helo=smtpout.laposte.net) by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <nicolas.sauzede@laposte.net>) id 1SUZ6O-0004Ek-Ue
	for qemu-devel@nongnu.org; Wed, 16 May 2012 03:56:57 -0400
Date: Wed, 16 May 2012 09:56:55 +0200
From: "nicolas.sauzede" <nicolas.sauzede@laposte.net>
Message-ID: <2052729756.454420.1337155011594.JavaMail.www@wwinf8304>
In-Reply-To: <4FB285A5.6030205@codemonkey.ws>
References: <1512121653.606644.1337094765947.JavaMail.www@wwinf8306>
	<4FB27400.3010908@suse.de>
	<27874590.608345.1337095907076.JavaMail.www@wwinf8306>
	<4FB285A5.6030205@codemonkey.ws>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [Qemu-devel] Get current env within io_handler ?
Reply-To: "nicolas.sauzede" <nicolas.sauzede@laposte.net>
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: Anthony Liguori <anthony@codemonkey.ws>
Cc: =?UTF-8?Q?Andreas_F=C3=A4rber?= <afaerber@suse.de>, qemu-devel@nongnu.org

> Yes, it's entirely intentional to prevent io handlers from accessing CPUS=
tate.
>=20
> For what you're doing, you need to hook more deeply into target-arm befor=
e the=20
> dispatch actually happens.

Ok, but then I guess that this kind of hooks may be less generic than the t=
raditional
"io_handler" I used for my qemu/TLM binding, right ?
Are there any example code showing such kind of hooks in qemu source ?
And is this method advisable, in term of maintenance, etc. ?
(what if we want to support multiple qemu targets, should we duplicate hook=
s code ?)

> Regards,
>=20
> Anthony Liguori

Thanks for your support,
NS.


Une messagerie gratuite, garantie =C3=A0 vie et des services en plus, =C3=
=A7a vous tente ?
Je cr=C3=A9e ma bo=C3=AEte mail www.laposte.net