From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: Pass (sender SPF authorized) identity=mailfrom; client-ip=162.221.156.55; helo=smtp03.citrix.com; envelope-from=prvs=969ce9b1e=anthony.perard@citrix.com; receiver=edk2-devel@lists.01.org Received: from SMTP03.CITRIX.COM (smtp03.citrix.com [162.221.156.55]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 9F9CC2194EB76 for ; Thu, 14 Mar 2019 10:41:32 -0700 (PDT) X-IronPort-AV: E=Sophos;i="5.58,478,1544486400"; d="scan'208";a="80599801" Date: Thu, 14 Mar 2019 17:41:21 +0000 From: Anthony PERARD To: Igor Druzhinin CC: , , , , , Message-ID: <20190314174121.GB11621@perard.uk.xensource.com> References: <1551876056-28223-1-git-send-email-igor.druzhinin@citrix.com> <1551876056-28223-2-git-send-email-igor.druzhinin@citrix.com> MIME-Version: 1.0 In-Reply-To: <1551876056-28223-2-git-send-email-igor.druzhinin@citrix.com> User-Agent: Mutt/1.11.3 (2019-02-01) Subject: Re: [PATCH RESEND 1/3] OvmfPkg/XenSupport: remove usage of prefetchable PCI host bridge aperture X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Mar 2019 17:41:36 -0000 X-List-Received-Date: Thu, 14 Mar 2019 17:41:36 -0000 X-List-Received-Date: Thu, 14 Mar 2019 17:41:36 -0000 X-List-Received-Date: Thu, 14 Mar 2019 17:41:36 -0000 X-List-Received-Date: Thu, 14 Mar 2019 17:41:36 -0000 X-List-Received-Date: Thu, 14 Mar 2019 17:41:36 -0000 X-List-Received-Date: Thu, 14 Mar 2019 17:41:36 -0000 X-List-Received-Date: Thu, 14 Mar 2019 17:41:36 -0000 X-List-Received-Date: Thu, 14 Mar 2019 17:41:36 -0000 X-List-Received-Date: Thu, 14 Mar 2019 17:41:36 -0000 X-List-Received-Date: Thu, 14 Mar 2019 17:41:36 -0000 X-List-Received-Date: Thu, 14 Mar 2019 17:41:36 -0000 X-List-Received-Date: Thu, 14 Mar 2019 17:41:36 -0000 X-List-Received-Date: Thu, 14 Mar 2019 17:41:36 -0000 X-List-Received-Date: Thu, 14 Mar 2019 17:41:36 -0000 X-List-Received-Date: Thu, 14 Mar 2019 17:41:36 -0000 X-List-Received-Date: Thu, 14 Mar 2019 17:41:36 -0000 X-List-Received-Date: Thu, 14 Mar 2019 17:41:36 -0000 X-List-Received-Date: Thu, 14 Mar 2019 17:41:36 -0000 X-List-Received-Date: Thu, 14 Mar 2019 17:41:36 -0000 X-List-Received-Date: Thu, 14 Mar 2019 17:41:36 -0000 X-List-Received-Date: Thu, 14 Mar 2019 17:41:36 -0000 X-List-Received-Date: Thu, 14 Mar 2019 17:41:36 -0000 X-List-Received-Date: Thu, 14 Mar 2019 17:41:36 -0000 X-List-Received-Date: Thu, 14 Mar 2019 17:41:36 -0000 X-List-Received-Date: Thu, 14 Mar 2019 17:41:36 -0000 X-List-Received-Date: Thu, 14 Mar 2019 17:41:36 -0000 X-List-Received-Date: Thu, 14 Mar 2019 17:41:36 -0000 X-List-Received-Date: Thu, 14 Mar 2019 17:41:36 -0000 X-List-Received-Date: Thu, 14 Mar 2019 17:41:36 -0000 X-List-Received-Date: Thu, 14 Mar 2019 17:41:36 -0000 X-List-Received-Date: Thu, 14 Mar 2019 17:41:36 -0000 X-List-Received-Date: Thu, 14 Mar 2019 17:41:36 -0000 X-List-Received-Date: Thu, 14 Mar 2019 17:41:36 -0000 X-List-Received-Date: Thu, 14 Mar 2019 17:41:36 -0000 X-List-Received-Date: Thu, 14 Mar 2019 17:41:36 -0000 X-List-Received-Date: Thu, 14 Mar 2019 17:41:36 -0000 X-List-Received-Date: Thu, 14 Mar 2019 17:41:36 -0000 X-List-Received-Date: Thu, 14 Mar 2019 17:41:36 -0000 X-List-Received-Date: Thu, 14 Mar 2019 17:41:36 -0000 X-List-Received-Date: Thu, 14 Mar 2019 17:41:36 -0000 X-List-Received-Date: Thu, 14 Mar 2019 17:41:36 -0000 X-List-Received-Date: Thu, 14 Mar 2019 17:41:36 -0000 X-List-Received-Date: Thu, 14 Mar 2019 17:41:36 -0000 X-List-Received-Date: Thu, 14 Mar 2019 17:41:36 -0000 X-List-Received-Date: Thu, 14 Mar 2019 17:41:36 -0000 X-List-Received-Date: Thu, 14 Mar 2019 17:41:36 -0000 X-List-Received-Date: Thu, 14 Mar 2019 17:41:36 -0000 X-List-Received-Date: Thu, 14 Mar 2019 17:41:36 -0000 X-List-Received-Date: Thu, 14 Mar 2019 17:41:36 -0000 X-List-Received-Date: Thu, 14 Mar 2019 17:41:36 -0000 X-List-Received-Date: Thu, 14 Mar 2019 17:41:36 -0000 X-List-Received-Date: Thu, 14 Mar 2019 17:41:36 -0000 X-List-Received-Date: Thu, 14 Mar 2019 17:41:36 -0000 X-List-Received-Date: Thu, 14 Mar 2019 17:41:36 -0000 X-List-Received-Date: Thu, 14 Mar 2019 17:41:36 -0000 X-List-Received-Date: Thu, 14 Mar 2019 17:41:36 -0000 X-List-Received-Date: Thu, 14 Mar 2019 17:41:36 -0000 X-List-Received-Date: Thu, 14 Mar 2019 17:41:36 -0000 X-List-Received-Date: Thu, 14 Mar 2019 17:41:36 -0000 X-List-Received-Date: Thu, 14 Mar 2019 17:41:36 -0000 X-List-Received-Date: Thu, 14 Mar 2019 17:41:36 -0000 X-List-Received-Date: Thu, 14 Mar 2019 17:41:36 -0000 X-List-Received-Date: Thu, 14 Mar 2019 17:41:36 -0000 X-List-Received-Date: Thu, 14 Mar 2019 17:41:36 -0000 X-List-Received-Date: Thu, 14 Mar 2019 17:41:36 -0000 X-List-Received-Date: Thu, 14 Mar 2019 17:41:36 -0000 X-List-Received-Date: Thu, 14 Mar 2019 17:41:36 -0000 X-List-Received-Date: Thu, 14 Mar 2019 17:41:36 -0000 X-List-Received-Date: Thu, 14 Mar 2019 17:41:36 -0000 X-List-Received-Date: Thu, 14 Mar 2019 17:41:36 -0000 X-List-Received-Date: Thu, 14 Mar 2019 17:41:36 -0000 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline Hi, On Wed, Mar 06, 2019 at 12:40:54PM +0000, Igor Druzhinin wrote: > This aperture doesn't exist in OVMF and trying to use it causes I'm trying to understand what you mean by writing "doesn't exist in OVMF". Are prefetchable BAR not handled by ScanForRootBridges() ? Or is it the emulation of the config space that isn't correct? Maybe QEMU should lies about a BAR been prefetchable? This patch feels like a workaround, but maybe I'm wrong. Thanks. > failing assertions later in cases there are prefetchable and > non-prefetchable BARs following each other. This configuration is > quite likely with some PCI passthrough devices. -- Anthony PERARD