Date: Thu, 16 Jul 2020 07:07:12 +0000 From: bugzilla-noreply@freebsd.org To: virtualization@FreeBSD.org Subject: [Bug 222996] FreeBSD 11.1-12 on Hyper-V with PCI Express Pass Through Message-ID: <bug-222996-27103-Rz81NQHgWO@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-222996-27103@https.bugs.freebsd.org/bugzilla/> References: <bug-222996-27103@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=3D222996 --- Comment #36 from Wei Hu <weh@microsoft.com> --- (In reply to Dexuan Cui from comment #35) On Gen1, the system provided pcib driver grabs these mmio addresses way ear= lier than vmbus comes up. I then allocates the address to the vga driver: pcib0: allocated type 3 (0xf8000000-0xfbffffff) for rid 10 of pci0:0:8:0 This happened before vmbus comes up. On Gen2 I just look at my test VM without having a passthrough deivce. Ther= e is no pcib device comes before vmbus loading. The efifb (framebuffer) driver is loaded before vmbus but it doesn't show which mmio address it is using. When vmbus comes up it gets the address: vmbus0: decoding 3 range 0xf8000000-0xfed3ffff I am not sure whether the passthrough device comes before or after vmbus is loaded. If it comes before, then this patch may not work. We may need to reserve the address before the passthrough device asks for mmio address. On= ce Dmitry has the environment we can find out. The bad address we know now is just 8MB (0xf8000000 - 0xf87fffff). I think = the default maximum space HyperV gives for frame buffer is 64MB which should be= ok. --=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-222996-27103-Rz81NQHgWO>