From: "nicolas.sauzede" <nicolas.sauzede@laposte.net>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: "Andreas Färber" <afaerber@suse.de>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Get current env within io_handler ?
Date: Wed, 16 May 2012 09:56:55 +0200 [thread overview]
Message-ID: <2052729756.454420.1337155011594.JavaMail.www@wwinf8304> (raw)
In-Reply-To: <4FB285A5.6030205@codemonkey.ws>
> 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.
Ok, but then I guess that this kind of hooks may be less generic than the traditional
"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 hooks code ?)
> Regards,
>
> Anthony Liguori
Thanks for your support,
NS.
Une messagerie gratuite, garantie à vie et des services en plus, ça vous tente ?
Je crée ma boîte mail www.laposte.net
prev parent reply other threads:[~2012-05-16 7:57 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
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 [this message]
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=2052729756.454420.1337155011594.JavaMail.www@wwinf8304 \
--to=nicolas.sauzede@laposte.net \
--cc=afaerber@suse.de \
--cc=anthony@codemonkey.ws \
--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).