From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751300AbcGNOYl (ORCPT ); Thu, 14 Jul 2016 10:24:41 -0400 Received: from mga03.intel.com ([134.134.136.65]:48356 "EHLO mga03.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750897AbcGNOYk (ORCPT ); Thu, 14 Jul 2016 10:24:40 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.28,363,1464678000"; d="scan'208";a="734219534" Subject: Re: [PATCH 4/4] x86: use pte_none() to test for empty PTE To: Vlastimil Babka , Dave Hansen , linux-kernel@vger.kernel.org References: <20160708001909.FB2443E2@viggo.jf.intel.com> <20160708001915.813703D9@viggo.jf.intel.com> <71d7b63a-45dd-c72d-a277-03124b0053ae@suse.cz> Cc: x86@kernel.org, linux-mm@kvack.org, torvalds@linux-foundation.org, akpm@linux-foundation.org, bp@alien8.de, ak@linux.intel.com, mhocko@suse.com, dave.hansen@linux.intel.com, Boris Ostrovsky , David Vrabel , Juergen Gross From: Dave Hansen Message-ID: <5787A0A2.4070406@intel.com> Date: Thu, 14 Jul 2016 07:24:34 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.8.0 MIME-Version: 1.0 In-Reply-To: <71d7b63a-45dd-c72d-a277-03124b0053ae@suse.cz> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 07/14/2016 06:47 AM, Vlastimil Babka wrote: > So, this might be just because I know next to nothing about (para)virt, > but... > > in arch/x86/include/asm/paravirt.h, pte_val is implemented via some > pvops, which suggests that obtaining a pte value is different than just > reading it from memory. But I don't see pte_none() defined to be using > this on paravirt, and it shares (before patch 2/4) the "return !pte.pte" > implementation, AFAICS? > > So that itself is suspicious to me. And now that this patches does > things like this: > > - if (pte_val(*pte)) { > + if (!pte_none(*pte)) { > > So previously on paravirt these tests would read pte via the pvops, and > now they won't. Is that OK? I've cc'd a few Xen guys. I think they're the only ones that would care. But, as far as I can tell, the Xen pte_val() will take a _PAGE_PRESENT PTE and muck with it. But its answer will never differ for an all 0 PTE from !pte_none() because that PTE does not have _PAGE_PRESENT set. It does seem fragile that Xen is doing it this way, but I guess it works.