From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1O2duP-0006I2-4F
	for qemu-devel@nongnu.org; Fri, 16 Apr 2010 01:16:05 -0400
Received: from [140.186.70.92] (port=54719 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1O2duM-0006GP-RU
	for qemu-devel@nongnu.org; Fri, 16 Apr 2010 01:16:03 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69)
	(envelope-from <junkoi2004@gmail.com>) id 1O2duL-0007w2-JB
	for qemu-devel@nongnu.org; Fri, 16 Apr 2010 01:16:02 -0400
Received: from mail-iw0-f194.google.com ([209.85.223.194]:50481)
	by eggs.gnu.org with esmtp (Exim 4.69)
	(envelope-from <junkoi2004@gmail.com>) id 1O2duL-0007vv-FN
	for qemu-devel@nongnu.org; Fri, 16 Apr 2010 01:16:01 -0400
Received: by iwn32 with SMTP id 32so1117592iwn.18
	for <qemu-devel@nongnu.org>; Thu, 15 Apr 2010 22:16:00 -0700 (PDT)
MIME-Version: 1.0
In-Reply-To: <t2hfdaac4d51004151949i834ca829z8c1cf78ed4457463@mail.gmail.com>
References: <t2hfdaac4d51004151949i834ca829z8c1cf78ed4457463@mail.gmail.com>
From: Jun Koi <junkoi2004@gmail.com>
Date: Fri, 16 Apr 2010 14:15:40 +0900
Message-ID: <x2pfdaac4d51004152215z33db8143me575ab64c99ad3c5@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Subject: [Qemu-devel] Re: TLB entry with separate addr_{read|write|code}?
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org

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