From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id B3A59C433EF for ; Wed, 13 Jul 2022 10:30:06 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236006AbiGMKaE (ORCPT ); Wed, 13 Jul 2022 06:30:04 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:53316 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231241AbiGMK34 (ORCPT ); Wed, 13 Jul 2022 06:29:56 -0400 Received: from mga05.intel.com (mga05.intel.com [192.55.52.43]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 1756EE5842; Wed, 13 Jul 2022 03:29:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1657708196; x=1689244196; h=message-id:subject:from:to:cc:date:in-reply-to: references:content-transfer-encoding:mime-version; bh=xCPTZdPlr/QKclHnOwFieHwilG0LSlbmNN9362YdJ2k=; b=MyKRjAo4mnJiCq/UzI/B+Mhr5EoErog+xjUQeBiyWETk9DmLjW8OjUv0 ebF6J3WRAF26fPfwEUEK90TmbuT4QO80Wvc6u9HQpv0z4XG7rXanygQ77 jxMp2kSs3wCHPgEO37wJx+eMSDUn/Yojl9QbDkPWFU0MZ6sygfvnMrWC4 Go5q7eLvlOrYC9mijQHBuxpXcQ+o/klSnf5+fTydBChN4qzPV+GzwZ9h7 Mwngom/J/7YXhXHC3okFLJEKnVeeUdQVVC0KUevC9BYVUwGN3636VRcjZ Jp/dyRqsJbUSWwWdsh15Yi4YycX3P8JPWjJ2huxX4wq6DJusBj2QSErDa Q==; X-IronPort-AV: E=McAfee;i="6400,9594,10406"; a="371486768" X-IronPort-AV: E=Sophos;i="5.92,267,1650956400"; d="scan'208";a="371486768" Received: from orsmga006.jf.intel.com ([10.7.209.51]) by fmsmga105.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 13 Jul 2022 03:29:55 -0700 X-IronPort-AV: E=Sophos;i="5.92,267,1650956400"; d="scan'208";a="570574395" Received: from ifatima-mobl1.amr.corp.intel.com (HELO khuang2-desk.gar.corp.intel.com) ([10.212.1.196]) by orsmga006-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 13 Jul 2022 03:29:54 -0700 Message-ID: <753184425e9d613841f4870a8a69f8cf96832f8d.camel@intel.com> Subject: Re: [PATCH v7 035/102] KVM: x86/mmu: Explicitly check for MMIO spte in fast page fault From: Kai Huang To: Isaku Yamahata Cc: isaku.yamahata@intel.com, kvm@vger.kernel.org, linux-kernel@vger.kernel.org, Paolo Bonzini , Sean Christopherson Date: Wed, 13 Jul 2022 22:29:51 +1200 In-Reply-To: <20220713083515.GQ1379820@ls.amr.corp.intel.com> References: <71e4c19d1dff8135792e6c5a17d3a483bc99875b.1656366338.git.isaku.yamahata@intel.com> <20220713083515.GQ1379820@ls.amr.corp.intel.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.44.3 (3.44.3-1.fc36) MIME-Version: 1.0 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org >=20 > Although it was needed, I noticed the following commit made this patch > unnecessary. So I'll drop this patch. Kudos to Sean. >=20 > edea7c4fc215c7ee1cc98363b016ad505cbac9f7 > "KVM: x86/mmu: Use a dedicated bit to track shadow/MMU-present SPTEs" >=20 Yes is_shadow_present_pte() always return false for MMIO so this patch isn'= t needed anymore.