Re: Enabling VIMAGE by default for FreeBSD 11?
On 10/17/14, 7:51 PM, Marko Zec wrote: On Fri, 17 Oct 2014 13:37:37 +0200 Marius Strobl wrote: On Wed, Oct 15, 2014 at 04:27:28PM -0700, Craig Rodrigues wrote: On Sun, Oct 12, 2014 at 6:35 AM, Kris Moore wrote: It was for a while in 9.2, but we removed it from 10.0 and later due to stability issues we kept getting reports about. Haven't tried it since then, dont know if those issues are fixed. I fixed some of the problems with VIMAGE that I encountered with Bluetooth: https://lists.freebsd.org/pipermail/svn-src-head/2013-July/049582.html ... which still lacks a proper implementation that doesn't constitute a gross layering violation in generic bus code. By all means please go ahead and propose a layering-clean alternative, not as ugly and intrusive as this part which I assume bodes you eyes: - return (device_attach(dev)); + + CURVNET_SET_QUIET(vnet0); + error = device_attach(dev); + CURVNET_RESTORE(); + return error; Marko I think he means the entire bluetooth implementation, which is done from within netgraph. Hiroo Onoo submitted this patch, which I committed to fix problems with VIMAGE encountered with removable USB Ethernet: https://lists.freebsd.org/pipermail/svn-src-all/2014-February/081025.html Martin Matuska committed this fix for PF: https://lists.freebsd.org/pipermail/svn-src-head/2014-April/057803.html So a lot of the stability problems with VIMAGE which were in PC-BSD 9.2 and FreeBSD 9.x have been slowly been fixed. Marius ___ freebsd-...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org" ___ freebsd-...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org" ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
RE: io-apic interrupt migration on bhyve
Hi, On more analysis I found that there is a race condition in Guest OS such that before complete initialization happens for APs the interrupt migration takes place and hence incorrect cpu is written to io-apic's rte for that particular pin. The debug prints either in Guest OS or vmm just kills this race condition. Thanks. RegardsAshutosh > From: mrashut...@hotmail.com > To: freebsd-virtualization@freebsd.org > Subject: io-apic interrupt migration on bhyve > Date: Fri, 17 Oct 2014 13:24:34 + > > > > Hi, > > > > I am witnessing some strange behavior w.r.t io-apic > interrupt migration on bhyve. > > I have below assignment for a level triggered > interrupt: > > > > io-apic pin - p > > cpu vector - v > > cpu id - 0 > > > > when this interrupt is migrated to cpu 1 then > the assignment is as below > > > > io-apic pin - p > > cpu vector - v1 > > cpu id - 1 > > > > When VM boots up then OS is getting interrupts for > > > > io-apic pin - p > > cpu vector - v1 > > cpu id - 0 > > > > Added debug prints in vioapic_write function > to check the values written to io-apic rte for this pin and then VM gets > correct interrupts i.e (vector v, cpu 0 ) before the interrupts are migrated > and > (vector v1, cpu 1) after the migration When prints are removed then the > problem happens and we see interrupts for (vector v1 and cpu 0). > RegardsAshutosh > ___ > freebsd-virtualization@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to > "freebsd-virtualization-unsubscr...@freebsd.org" ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
io-apic interrupt migration on bhyve
Hi, I am witnessing some strange behavior w.r.t io-apic interrupt migration on bhyve. I have below assignment for a level triggered interrupt: io-apic pin - p cpu vector - v cpu id - 0 when this interrupt is migrated to cpu 1 then the assignment is as below io-apic pin - p cpu vector - v1 cpu id - 1 When VM boots up then OS is getting interrupts for io-apic pin - p cpu vector - v1 cpu id - 0 Added debug prints in vioapic_write function to check the values written to io-apic rte for this pin and then VM gets correct interrupts i.e (vector v, cpu 0 ) before the interrupts are migrated and (vector v1, cpu 1) after the migration When prints are removed then the problem happens and we see interrupts for (vector v1 and cpu 0). RegardsAshutosh ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: Enabling VIMAGE by default for FreeBSD 11?
On Fri, 17 Oct 2014 13:37:37 +0200 Marius Strobl wrote: > On Wed, Oct 15, 2014 at 04:27:28PM -0700, Craig Rodrigues wrote: > > On Sun, Oct 12, 2014 at 6:35 AM, Kris Moore wrote: > > > > > > > > It was for a while in 9.2, but we removed it from 10.0 and later > > > due to stability issues we kept getting reports about. Haven't > > > tried it since then, dont know if those issues are fixed. > > > > > > > I fixed some of the problems with VIMAGE that I encountered with > > Bluetooth: > > > > https://lists.freebsd.org/pipermail/svn-src-head/2013-July/049582.html > > ... which still lacks a proper implementation that doesn't constitute > a gross layering violation in generic bus code. By all means please go ahead and propose a layering-clean alternative, not as ugly and intrusive as this part which I assume bodes you eyes: - return (device_attach(dev)); + + CURVNET_SET_QUIET(vnet0); + error = device_attach(dev); + CURVNET_RESTORE(); + return error; Marko > > > > Hiroo Onoo submitted this patch, which I committed to fix problems > > with VIMAGE encountered with removable USB Ethernet: > > > > https://lists.freebsd.org/pipermail/svn-src-all/2014-February/081025.html > > > > Martin Matuska committed this fix for PF: > > https://lists.freebsd.org/pipermail/svn-src-head/2014-April/057803.html > > > > So a lot of the stability problems with VIMAGE which were in PC-BSD > > 9.2 and FreeBSD 9.x have been slowly been fixed. > > Marius > > ___ > freebsd-...@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org" ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: Enabling VIMAGE by default for FreeBSD 11?
On Wed, Oct 15, 2014 at 04:27:28PM -0700, Craig Rodrigues wrote: > On Sun, Oct 12, 2014 at 6:35 AM, Kris Moore wrote: > > > > > It was for a while in 9.2, but we removed it from 10.0 and later due to > > stability issues we kept getting reports about. Haven't tried it since > > then, dont know if those issues are fixed. > > > > I fixed some of the problems with VIMAGE that I encountered with Bluetooth: > > https://lists.freebsd.org/pipermail/svn-src-head/2013-July/049582.html ... which still lacks a proper implementation that doesn't constitute a gross layering violation in generic bus code. > > Hiroo Onoo submitted this patch, which I committed to fix problems with > VIMAGE encountered with removable USB Ethernet: > > https://lists.freebsd.org/pipermail/svn-src-all/2014-February/081025.html > > Martin Matuska committed this fix for PF: > https://lists.freebsd.org/pipermail/svn-src-head/2014-April/057803.html > > So a lot of the stability problems with VIMAGE which were in PC-BSD 9.2 and > FreeBSD 9.x have been slowly been fixed. Marius ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
