Received: by 2002:a05:6a10:9848:0:0:0:0 with SMTP id x8csp87525pxf; Tue, 6 Apr 2021 15:51:43 -0700 (PDT) X-Google-Smtp-Source: ABdhPJw/COhQMY/cVaBs4McsyUPj1aNCTnT7RzJpRRhRNa1D8kOiJvt9jKcr9kUQw0ZFVRYgHXrj X-Received: by 2002:a50:fb8c:: with SMTP id e12mr771689edq.295.1617749503103; Tue, 06 Apr 2021 15:51:43 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1617749503; cv=none; d=google.com; s=arc-20160816; b=ujZkDv028Shk+MHy2zloS+wqhkIzRQKuhfX8mroFFK7z6Wt0j3wDC9tf+fiCouh9nz lVcfSkCLEGaWNrIBrDNn2soUMurYe2X5TaBOowaXsJ4SWKdIADuBVblpM17vcakBZcT8 YcrfqJsTd5wWWkcl+cCL2t4uHm5B4vhpgqCYpEJmOfhxmXGfv+jDURPljRSHi82vDwPZ hlURBSsV4SsoBXC2Kp3mGZ6gWhlKmva3GRI4MR+8h0WX7Y6u8TVtofvX7PEpEke+xxmF kKCXDk5hvMdtiS+DTkGyXXVSzoTKu85irlqY5U9VHyMDeB6RVl3YBK76uGALwVVS6DRf fqbA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:subject:cc:to:from:date; bh=+pD40TzGl7wexujub1Nq05XqukMQkItB0idqY2w08vA=; b=vJPaxILOh14dob2xcsZ/MA83CLZE9drkO4ahzYp6i+4vcD+mlsw37vKwQSEgjBFcQ6 eo7W9TXILqRIDAM34bhlf5HnxyqK1eDwZ0T3xHgNMrG7wTiXjv5PammEeZQi2yPfNNyQ BBz/MKfr7j22FcoxmquSLWj8qj4HGeuXxw9zLruOMTcu0THz2UDXLxwr7g4OJot2zjvq buesy2g+EGz81m9Zu6FblKDLyrf7iiwLlu5FR05DBPtEle9pzeh4aRfiK+DgS2/J1aZI syUjy52xgq/jDCyYz0pejoiUplk/QKLoxNeNlongHR65OtZ6aUXcf2cbmDFUDM0DGE6S xFZw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=siemens.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id 4si19204511edc.316.2021.04.06.15.51.17; Tue, 06 Apr 2021 15:51:43 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=siemens.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1344677AbhDFNos (ORCPT + 99 others); Tue, 6 Apr 2021 09:44:48 -0400 Received: from lizzard.sbs.de ([194.138.37.39]:43233 "EHLO lizzard.sbs.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1344659AbhDFNon (ORCPT ); Tue, 6 Apr 2021 09:44:43 -0400 Received: from mail2.sbs.de (mail2.sbs.de [192.129.41.66]) by lizzard.sbs.de (8.15.2/8.15.2) with ESMTPS id 136DhfCQ018008 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 6 Apr 2021 15:43:41 +0200 Received: from md1za8fc.ad001.siemens.net ([167.87.42.66]) by mail2.sbs.de (8.15.2/8.15.2) with ESMTP id 136De2KZ031989; Tue, 6 Apr 2021 15:40:02 +0200 Date: Tue, 6 Apr 2021 15:40:01 +0200 From: Henning Schild To: "Enrico Weigelt, metux IT consult" Cc: Bjorn Helgaas , Andy Shevchenko , Wolfram Sang , Jean Delvare , "Lee Jones" , Tan Jui Nee , "Jim Quinlan" , Jonathan Yong , Bjorn Helgaas , , , , Jean Delvare , Peter Tyser , Subject: Re: [PATCH v1 3/7] PCI: New Primary to Sideband (P2SB) bridge support library Message-ID: <20210406154001.3eec0698@md1za8fc.ad001.siemens.net> In-Reply-To: <3f33a178-3002-e93e-89f1-8cf05097da25@metux.net> References: <20210309014221.GA1831206@bjorn-Precision-5520> <20210309094252.396b7f2d@md1za8fc.ad001.siemens.net> <3f33a178-3002-e93e-89f1-8cf05097da25@metux.net> X-Mailer: Claws Mail 3.17.8 (GTK+ 2.24.32; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Am Fri, 2 Apr 2021 15:09:12 +0200 schrieb "Enrico Weigelt, metux IT consult" : > On 09.03.21 09:42, Henning Schild wrote: > > > The device will respond to MMIO while being hidden. I am afraid > > nothing stops a collision, except for the assumption that the BIOS > > is always right and PCI devices never get remapped. But just > > guessing here. > > What could go wrong if it is remapped, except that this driver would > write to the wrong mmio space ? > > If it's unhidden, pci-core should see it and start the usual probing, > right ? I have seen this guy exposed to Linux on coreboot machines. No issues. But i can imagine BIOSs that somehow make use of the device and assume it wont move. So we would at least need a parameter to allow keeping that device hidden, or "fixed" in memory. Henning > > --mtx >