From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:43717) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YVl5L-0007Is-6E for qemu-devel@nongnu.org; Wed, 11 Mar 2015 14:10:28 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YVl5G-0006Kx-4d for qemu-devel@nongnu.org; Wed, 11 Mar 2015 14:10:23 -0400 Received: from mx1.redhat.com ([209.132.183.28]:38022) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YVl5F-0006Ko-RW for qemu-devel@nongnu.org; Wed, 11 Mar 2015 14:10:18 -0400 Date: Wed, 11 Mar 2015 19:10:12 +0100 From: Andrew Jones Message-ID: <20150311181011.GB10903@hawk.usersys.redhat.com> References: <1426021590-4834-1-git-send-email-drjones@redhat.com> <1426021590-4834-4-git-send-email-drjones@redhat.com> <20150311174241.GA10903@hawk.usersys.redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [Qemu-devel] [PATCH v2 3/3] target-arm: get_phys_addr_lpae: more xn control List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell Cc: QEMU Developers On Wed, Mar 11, 2015 at 05:49:39PM +0000, Peter Maydell wrote: > On 11 March 2015 at 17:42, Andrew Jones wrote: > > On Wed, Mar 11, 2015 at 05:02:00PM +0000, Peter Maydell wrote: > > >> > + if (is_aa64) { > >> > + switch (regime_el(env, mmu_idx)) { > >> > + case 1: > >> > + if (is_user && !user_rw) { > >> > + wxn = 0; > >> > >> I don't understand this. We ignore the WXN bit if this is > >> a user access and the page is not readable ? > > > > Yup. If the page is not readable or writeable, AP[1]=0. I almost > > submitted an errata to the ARM ARM when I saw this on the 2nd line > > of table D4-32. I thought it must be a typo. However I tested it > > on hardware, and it works this way. So at least the weirdness has > > been implemented consistently... > > Still confused. If the page isn't readable or writable > then WXN isn't going to kick in anyway because WXN only > affects writable pages. I don't see what the case is > where this bit of code will make a difference. > Ah, that is true. Too bad I didn't read this before sending v3, as I could have removed it, if you prefer. I had it here to be explicit about the ignoring of wxn - matching the spec, but you're right, it's useless code. Should I send a v4? drew