From owner-freebsd-acpi@freebsd.org Fri Mar 1 18:14:08 2019 Return-Path: Delivered-To: freebsd-acpi@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3D028151FC7A for ; Fri, 1 Mar 2019 18:14:08 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id C99FE8B240 for ; Fri, 1 Mar 2019 18:14:07 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 83B39151FC77; Fri, 1 Mar 2019 18:14:07 +0000 (UTC) Delivered-To: acpi@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 474DF151FC72 for ; Fri, 1 Mar 2019 18:14:07 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CF8F98B23B for ; Fri, 1 Mar 2019 18:14:06 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 07C967F53 for ; Fri, 1 Mar 2019 18:14:06 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x21IE5NF050510 for ; Fri, 1 Mar 2019 18:14:05 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x21IE5kL050502 for acpi@FreeBSD.org; Fri, 1 Mar 2019 18:14:05 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: acpi@FreeBSD.org Subject: [Bug 235876] ACPI related commit r330113 broke Microsoft Hyper-V passthrough device on Generation 2 FreeBSD VM Date: Fri, 01 Mar 2019 18:14:06 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 12.0-RELEASE X-Bugzilla-Keywords: needs-qa, regression X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: jhb@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: acpi@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Mar 2019 18:14:08 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D235876 --- Comment #7 from John Baldwin --- So this ASL is definitely using the flag explicitly. None of them are in ExtendedAddressSpaces, and some of them appear to be correct (e.g. the Host= -PCI bridge is using ResourceProducer in the way the non-arm-specific ACPI Host-= PCI bridge driver expects: to list ranges it decodes that are then used by child devices). It seems that a couple of the uses of ResourceProducer in this A= SL are just wrong though. First, numbers of times the flag is used vs not use= d: > grep ResourceConsumer tx2.asl | wc -l 53 > grep ResourceProducer tx2.asl | wc -l 11 Of those 11 cases, SB.ECAM is probably a consumer, not a producer, though we already treat acpi_sysres devices special. SB.PCI0 resources should be producers. If the committed patch actually wor= ked fully it would have broken booting completely since PCI0 would have claimed= all the resources for all its children blocking all of them from being able to alloc bars. We probably skip resources for PCI bridges which is why this m= ight still be working. The URT0 device's memory should be a consumer. Note that the interrupt resource is a consumer, and other similar devices use consumer. This is ju= st firmware writer incompetence. URT1, URT2, and URT3 are same as URT0. PCI1 is same as PCI0. So really, the real issue on the Cavium box is that the UART _CRS buffers h= ave a typo. I think the commit should be changed so that we just ignore 'ResourceProducer' on devices with the ARMH0011 _HID but otherwise leave it= in place. --=20 You are receiving this mail because: You are the assignee for the bug.=