Received: by 2002:a25:c593:0:0:0:0:0 with SMTP id v141csp5679856ybe; Tue, 17 Sep 2019 11:45:10 -0700 (PDT) X-Google-Smtp-Source: APXvYqyB2qEpxs8Nv3fkTIOuHYrXP7d3S7bmq724Xc2oNHySJTG+7UqIL80YXCcH7Fd47gVRqa1E X-Received: by 2002:aa7:c586:: with SMTP id g6mr6350220edq.38.1568745910170; Tue, 17 Sep 2019 11:45:10 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1568745910; cv=none; d=google.com; s=arc-20160816; b=YB32HJUjiOViWm9M41rWS3dIm3fVVT3D6jgz9AALSwV4Ptc9DBtRrq7tRHEn3maM0l AXDvG1jqUU3Nz4dOQlddilU91rQpNNv1tV9+/QLQ00tO6B+CkMG6J2Ashrtl2ptd6jD0 t2fFhZTQdXETtgsX4ETSelDPRvh1TKqJa1b//5tAA8AvjG7P1roxFJIKc6bLjE9hkgCG ts5Zwv7yW5ejFYb/j5FSvpLk0SXJYN1uMY9iwqFZc0WLBngVc5z7nuXztC7JLFE/Sa95 Mxso4d99tEJSGgCBelsPi/1kk5XyXeh7OCON15/fLB+x92fasPvD1p2OuEwhIrr2Cp2/ znIg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=jYrFdTEhZ1KjlwI1p17c+YQjPHV95x3aMS8BWmDnGho=; b=K0yzEDieK43u/p8IB8DvbAw5ka1/vnIC5MGScnKfqAjf5HOgzDakPxPbXDBEjFBWwv R3GxisB6pmWwmIQ50pn0NxpGPm2SLhOq7YPb61sZj+j9Q4MOLVVpnxi1Er3mMloBWe70 tcn7nd/nigfu2lcNuC5ZLL6uD6sdfT9QvpWyXFSCEhR4PatNi/bCyBWaRz9HgPzJS8FI yEWAn2uEilCC1eNbfKIYJHqoChQv0vJxNsHF52J1s2ZOROTUjpTA92TkLRJ4NL/GwqYl u21ZDPEBZWqKEB5aoebaI4Cv0iZkOd9JzODEGla57ASbuh0m3Y3JNhNpraWnE8G5irRq 9Hbw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id b8si1906130edc.231.2019.09.17.11.44.46; Tue, 17 Sep 2019 11:45:10 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728270AbfIQQhf (ORCPT + 99 others); Tue, 17 Sep 2019 12:37:35 -0400 Received: from foss.arm.com ([217.140.110.172]:58686 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727632AbfIQQhe (ORCPT ); Tue, 17 Sep 2019 12:37:34 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 4802828; Tue, 17 Sep 2019 09:37:34 -0700 (PDT) Received: from e121166-lin.cambridge.arm.com (e121166-lin.cambridge.arm.com [10.1.196.255]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 7977A3F575; Tue, 17 Sep 2019 09:37:33 -0700 (PDT) Date: Tue, 17 Sep 2019 17:37:24 +0100 From: Lorenzo Pieralisi To: "Derrick, Jonathan" Cc: "linux-kernel@vger.kernel.org" , "Busch, Keith" , "linux-pci@vger.kernel.org" , "helgaas@kernel.org" Subject: Re: [PATCH 2/2] PCI: vmd: Fix shadow offsets to reflect spec changes Message-ID: <20190917163716.GA9715@e121166-lin.cambridge.arm.com> References: <20190916135435.5017-1-jonathan.derrick@intel.com> <20190916135435.5017-3-jonathan.derrick@intel.com> <20190917104106.GB32602@e121166-lin.cambridge.arm.com> <87f1f92276becb6f83d040b36697ef8084e63105.camel@intel.com> <20190917140525.GA6377@e121166-lin.cambridge.arm.com> <087e23dc3bb7b94bb96c33b380732ebd1285e467.camel@intel.com> <20190917151523.GA7948@e121166-lin.cambridge.arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.4 (2018-02-28) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Sep 17, 2019 at 03:51:39PM +0000, Derrick, Jonathan wrote: [...] > Sorry for the confusion. > > These changes only affect systems with VMD devices with 8086:28C0 > device IDs, but these won't be production hardware for some time. > > Systems with VMD devices exist in the wild with 8086:201D device IDs. > These don't support the guest passthrough mode and this code won't > break anything with them. Additionally, patch 1/2 (bus numbering) only > affects 8086:28C0. > > So on existing HW, these patches won't affect anything It is me who created confusion, apologies. I read the code properly and I understand that both patches are fixes for HW that is still not available (and they can't create an issue with current kernel because HAS_MEMBAR_SHADOW and HAS_BUS_RESTRICTIONS features are not implemented on 8086:201D), we should take these patches and trickle them to stable kernels as soon as possible so that when HW _is_ available mainline and stable kernels are fixed. Correct ? Lorenzo