* [Qemu-devel] correct TCG_CALL_* flags for helpers which directly access env fields?
@ 2013-12-28 16:47 Peter Maydell
2013-12-30 14:48 ` Richard Henderson
0 siblings, 1 reply; 2+ messages in thread
From: Peter Maydell @ 2013-12-28 16:47 UTC (permalink / raw)
To: QEMU Developers; +Cc: Richard Henderson
Hi; just wanted to check my understanding of how the
TCG_CALL_* flags work.
In particular, for the fairly common case of helpers which
read or write fields in the CPU state via being passed an
'env' pointer, what are the correct flags? Assuming the fields
it accesses aren't also being used for TCG memory globals,
presumably NO_RWG_SE if the field is only read, and
NO_RWG if it's written?
thanks
-- PMM
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [Qemu-devel] correct TCG_CALL_* flags for helpers which directly access env fields?
2013-12-28 16:47 [Qemu-devel] correct TCG_CALL_* flags for helpers which directly access env fields? Peter Maydell
@ 2013-12-30 14:48 ` Richard Henderson
0 siblings, 0 replies; 2+ messages in thread
From: Richard Henderson @ 2013-12-30 14:48 UTC (permalink / raw)
To: Peter Maydell, QEMU Developers
On 12/28/2013 08:47 AM, Peter Maydell wrote:
> Assuming the fields
> it accesses aren't also being used for TCG memory globals,
> presumably NO_RWG_SE if the field is only read, and
> NO_RWG if it's written?
Correct.
r~
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2013-12-30 14:48 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-12-28 16:47 [Qemu-devel] correct TCG_CALL_* flags for helpers which directly access env fields? Peter Maydell
2013-12-30 14:48 ` Richard Henderson
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).