* [Qemu-devel] TLB entry with separate addr_{read|write|code}?
@ 2010-04-16 2:49 Jun Koi
2010-04-16 5:15 ` [Qemu-devel] " Jun Koi
0 siblings, 1 reply; 2+ messages in thread
From: Jun Koi @ 2010-04-16 2:49 UTC (permalink / raw)
To: qemu-devel
Hi,
In the TLB entry, why do we need to maintain separately addr_read,
addr_write and addr_code? Is it impossible to have only one for all
the purposes?
As far as I can see in tlb_set_page(), these fields are mutually
exclusive, as they either enable or get invalid value (-1).
Thanks,
Jun
^ permalink raw reply [flat|nested] 2+ messages in thread* [Qemu-devel] Re: TLB entry with separate addr_{read|write|code}?
2010-04-16 2:49 [Qemu-devel] TLB entry with separate addr_{read|write|code}? Jun Koi
@ 2010-04-16 5:15 ` Jun Koi
0 siblings, 0 replies; 2+ messages in thread
From: Jun Koi @ 2010-04-16 5:15 UTC (permalink / raw)
To: qemu-devel
On Fri, Apr 16, 2010 at 11:49 AM, Jun Koi <junkoi2004@gmail.com> wrote:
> Hi,
>
> In the TLB entry, why do we need to maintain separately addr_read,
> addr_write and addr_code? Is it impossible to have only one for all
> the purposes?
>
> As far as I can see in tlb_set_page(), these fields are mutually
> exclusive, as they either enable or get invalid value (-1).
Hmm I looked at the code again, and the attributes can be read, write
and execute at the same time.
Thanks,
J
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2010-04-16 5:16 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-04-16 2:49 [Qemu-devel] TLB entry with separate addr_{read|write|code}? Jun Koi
2010-04-16 5:15 ` [Qemu-devel] " Jun Koi
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).