From: "nicolas.sauzede" <nicolas.sauzede@laposte.net>
To: qemu-devel@nongnu.org
Cc: Blue Swirl <blauwirbel@gmail.com>
Subject: Re: [Qemu-devel] Get current env within io_handler ?
Date: Wed, 16 May 2012 09:58:28 +0200 [thread overview]
Message-ID: <189253069.454583.1337155108168.JavaMail.www@wwinf8304> (raw)
In-Reply-To: <4FB28591.4090709@suse.de>
> First, please don't top-post and please don't use HTML emails.
Sorry about that.
> Yes, there is work towards getting rid of implicit AREG0 env. This will
> be leading towards removing the register-pinned AREG0.
Will this AREG0 removal be optional/configurable if the patches hit the mainstream ?
> So you should rather figure out why you want to tie emulation of devices
> to the CPU requesting it.
Well, for example, we have the issue where we need to know if the cpu that performs a hardware io is in priviledged/secure more, because some HW devices implemented in TLM requires such special flags on certain register accesses.
How can we know that access property, when called back into an "io_handler" ?
Also, I think about some specific IPs such as local timers and such, all seen at the same address by all the smp cpu, then how can we know what cpu number originated the io transaction ?
> Andreas
>
Thanks again,
NS.
Une messagerie gratuite, garantie à vie et des services en plus, ça vous tente ?
Je crée ma boîte mail www.laposte.net
next prev parent reply other threads:[~2012-05-16 7:58 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 [this message]
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=189253069.454583.1337155108168.JavaMail.www@wwinf8304 \
--to=nicolas.sauzede@laposte.net \
--cc=blauwirbel@gmail.com \
--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).