Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 21 Feb 2019 22:49:06 +0000
From:      bugzilla-noreply@freebsd.org
To:        acpi@FreeBSD.org
Subject:   [Bug 235876] ACPI related commit r330133 broke Microsoft Hyper-V passthrough device on Generation 2 FreeBSD VM
Message-ID:  <bug-235876-16045-FRbGVaZFuI@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-235876-16045@https.bugs.freebsd.org/bugzilla/>
References:  <bug-235876-16045@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D235876

--- Comment #3 from John Baldwin <jhb@FreeBSD.org> ---
Hmm, so I rechecked the spec and while it does say that bit 0 is ignored, t=
he
spec also includes QWordMemory which explicitly mentions the producer/consu=
mer
flag (e.g. 19.6.111).  Andrew, do you have the acpidump of the Cavium box t=
hat
was affected by this?  It seems it was setting a reserved bit and relying on
that reserved bit being ignored, whereas in this case Hyper-V and is setting
the bit and relying on it being treated the same as it would be treated for
other resource types?  Both are undefined behavior, but the Cavium behavior
seems to be more weird (setting a reserved bit and hoping it is ignored).=20
Perhaps we can put '#ifdef __arm64__' around the res->Type part of the chec=
k?

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-235876-16045-FRbGVaZFuI>