From owner-freebsd-hackers@freebsd.org  Thu Oct 26 13:20:32 2017
Return-Path: <owner-freebsd-hackers@freebsd.org>
Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id DBC20E495D7
 for <freebsd-hackers@mailman.ysv.freebsd.org>;
 Thu, 26 Oct 2017 13:20:32 +0000 (UTC) (envelope-from rb@gid.co.uk)
Received: from mx0.gid.co.uk (mx0.gid.co.uk [194.32.164.250])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 6A3BF7DBDB
 for <freebsd-hackers@freebsd.org>; Thu, 26 Oct 2017 13:20:31 +0000 (UTC)
 (envelope-from rb@gid.co.uk)
Received: from [194.32.164.27] ([194.32.164.27])
 by mx0.gid.co.uk (8.14.2/8.14.2) with ESMTP id v9QDKOaZ045359
 for <freebsd-hackers@freebsd.org>; Thu, 26 Oct 2017 14:20:24 +0100 (BST)
 (envelope-from rb@gid.co.uk)
From: Bob Bishop <rb@gid.co.uk>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: hw.pci.realloc_bars
Message-Id: <A7DF03C1-C5AE-4A69-ACAB-ADAD3003722A@gid.co.uk>
Date: Thu, 26 Oct 2017 14:20:23 +0100
To: FreeBSD Hackers <freebsd-hackers@freebsd.org>
X-Mailer: Apple Mail (2.3273)
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
 <freebsd-hackers.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-hackers>, 
 <mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers/>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
 <mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Oct 2017 13:20:33 -0000

Hi,

hw.pci.realloc_bars controls a mechanism that repositions a PCI memory =
resource if it can=E2=80=99t be successfully allocated at the default =
place.

It=E2=80=99s disabled by default - anyone know why?

Seems to me that because it only comes into play in an error case it =
would be harmless to have it enabled by default. That would have avoided =
a recent case where installation on the HPE Gen 10 microserver is tricky =
because its VGA suffers from this problem.

Thoughts?

--
Bob Bishop
rb@gid.co.uk