Jenkins build is still unstable: FreeBSD_HEAD-tests2 #519
See https://jenkins.freebsd.org/job/FreeBSD_HEAD-tests2/519/ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [RFC] Start SMP subsystem earlier
On 01/05/15 14:43, Konstantin Belousov wrote: On Mon, Jan 05, 2015 at 02:18:17PM +0100, Hans Petter Selasky wrote: Hi, There is a limitiation on the number of interrupt vectors available when only a single processor is running. To have more interrupts available we need to start SMP earlier when building a monotolith kernel and not loading drivers as modules. The driver in question is a network driver and because it cannot be started after SI_SUB_ROOT_CONF due to PXE support I see no other option than to move SI_SUB_SMP earlier. Suggested patch: Index: sys/kernel.h === --- sys/kernel.h(revision 276691) +++ sys/kernel.h(working copy) @@ -152,6 +152,7 @@ SI_SUB_KPROF= 0x900,/* kernel profiling*/ SI_SUB_KICK_SCHEDULER = 0xa00,/* start the timeout events*/ SI_SUB_INT_CONFIG_HOOKS = 0xa80,/* Interrupts enabled config */ + SI_SUB_SMP = 0xa85,/* start the APs*/ SI_SUB_ROOT_CONF= 0xb00,/* Find root devices */ SI_SUB_DUMP_CONF= 0xb20,/* Find dump devices */ SI_SUB_RAID = 0xb38,/* Configure GEOM classes */ @@ -165,7 +166,6 @@ SI_SUB_KTHREAD_BUF = 0xea0,/* buffer daemon*/ SI_SUB_KTHREAD_UPDATE = 0xec0,/* update daemon*/ SI_SUB_KTHREAD_IDLE = 0xee0,/* idle procs*/ - SI_SUB_SMP = 0xf00,/* start the APs*/ SI_SUB_RACCTD = 0xf10,/* start racctd*/ SI_SUB_LAST = 0xfff /* final initialization */ }; Did you inspected all reordered sysinit routines and ensured that the reordering is safe ? At very least, SUB_SMP starts event timers, while KTHREAD_IDLE is about configuring some hardware which might be required/not ready for that. Hi, I did not inspect everything myself yet regarding this change. That's why I'm sending this e-mail out. The problem is simply that the total number of interrupts appears to be limited by APIC_NUM_IOINTS and NUM_IO_INTS which is per CPU from what I understand. Until SMP is activated the newbus code is simply distributing the IRQ vectors on the available IRQs, then when SMP is up it is re-shuffling them all. I was initially thinking that a hack might be possible, like using RF_SHARED for the IRQ resource, but then noticed that we were using MSI interrupts, which are not allocated in the same manner. The other issue is that the IRQs should be functional too, so that PXE boot can work. --HPS This fixes a problem for Mellanox drivers in the OFED layer. Possibly we need to move the SMP even earlier to not miss the generic FreeBSD PCI device enumeration or maybe this is not possible. Does anyone know how early we can start SMP? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
vt and VirtualBox?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Is here any possibility to add virtualbox driver to vt? Now console of -CURRENT guest in VirtualBox (using vga driver) is almost unusable slow! I'm not sure, that VirtualBox has API for paravirtualized screen output, though (guest addons?). - -- // Lev Serebryakov AKA Black Lion -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (MingW32) iQJ8BAEBCgBmBQJUqooJXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRGOTZEMUNBMEI1RjQzMThCNjc0QjMzMEFF QUIwM0M1OEJGREM0NzhGAAoJEOqwPFi/3EePKr0P/R1zqoNqgda2PjWrOwZYeCed gwWVzSEahFsxd+qNpEeKVXvcD4MP8oFMMjUsoNOqf9jonk3vVkzDfpHwHziRxBxL KhojqPvONZH75WF0PREOpx8/Ff3wtuZNggeyShZPb4ZiyZkXTScDxxn5ZhzGjDG4 OWViWEGK1Sw8U7gbyXPZs2D5B5kcExK5NFQyyIEnaRkGhwqHUCRsa5UP1we0QMsw YB8XswSf0z9GqpGv0KYSJqFqieSsxmzt3fE34vGTVE+vm1LToEdq6hWkHAgACuqa KmpAxaam1L4adH+SaPI9jMfpaPChE3RhwUpKMhexy64basyCC49yvXLXiF/28K35 ztsknr8tBmSv3lvMAFyxJqjZiq34WR7PcAbiPCLPy7FPwmvwbx6CSf1lUs96nuOw MfHB1eRzOlA2ABz/WwXMBKEmzNUdAsV1X1ILaCpRPQdDy2liIQpqsiNQS83obfw3 8pY+y7BH0hmI5auUbC5sk/kE/YbmAwoqS7FygV7rujb7pAOJQ6e4MlyTC3+pA+3J Qjspxe0YfOXO+tIH5/ydFMvZPGvrDwh+gx50d5INKAk57DFWzV4qCxnjYjJIbXys pifLOV2oh2sURd4atMEG2SfN8gYeDHMzOeav7sFo7XIM1S+9/i33LG9iSXwpukec eOjKYLgaSeGEy24lgCLs =tA47 -END PGP SIGNATURE- ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
[RFC] Start SMP subsystem earlier
Hi, There is a limitiation on the number of interrupt vectors available when only a single processor is running. To have more interrupts available we need to start SMP earlier when building a monotolith kernel and not loading drivers as modules. The driver in question is a network driver and because it cannot be started after SI_SUB_ROOT_CONF due to PXE support I see no other option than to move SI_SUB_SMP earlier. Suggested patch: Index: sys/kernel.h === --- sys/kernel.h(revision 276691) +++ sys/kernel.h(working copy) @@ -152,6 +152,7 @@ SI_SUB_KPROF= 0x900,/* kernel profiling*/ SI_SUB_KICK_SCHEDULER = 0xa00,/* start the timeout events*/ SI_SUB_INT_CONFIG_HOOKS = 0xa80,/* Interrupts enabled config */ + SI_SUB_SMP = 0xa85,/* start the APs*/ SI_SUB_ROOT_CONF= 0xb00,/* Find root devices */ SI_SUB_DUMP_CONF= 0xb20,/* Find dump devices */ SI_SUB_RAID = 0xb38,/* Configure GEOM classes */ @@ -165,7 +166,6 @@ SI_SUB_KTHREAD_BUF = 0xea0,/* buffer daemon*/ SI_SUB_KTHREAD_UPDATE = 0xec0,/* update daemon*/ SI_SUB_KTHREAD_IDLE = 0xee0,/* idle procs*/ - SI_SUB_SMP = 0xf00,/* start the APs*/ SI_SUB_RACCTD = 0xf10,/* start racctd*/ SI_SUB_LAST = 0xfff /* final initialization */ }; This fixes a problem for Mellanox drivers in the OFED layer. Possibly we need to move the SMP even earlier to not miss the generic FreeBSD PCI device enumeration or maybe this is not possible. Does anyone know how early we can start SMP? --HPS ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [RFC] Start SMP subsystem earlier
On Mon, Jan 05, 2015 at 02:18:17PM +0100, Hans Petter Selasky wrote: Hi, There is a limitiation on the number of interrupt vectors available when only a single processor is running. To have more interrupts available we need to start SMP earlier when building a monotolith kernel and not loading drivers as modules. The driver in question is a network driver and because it cannot be started after SI_SUB_ROOT_CONF due to PXE support I see no other option than to move SI_SUB_SMP earlier. Suggested patch: Index: sys/kernel.h === --- sys/kernel.h(revision 276691) +++ sys/kernel.h(working copy) @@ -152,6 +152,7 @@ SI_SUB_KPROF= 0x900,/* kernel profiling*/ SI_SUB_KICK_SCHEDULER = 0xa00,/* start the timeout events*/ SI_SUB_INT_CONFIG_HOOKS = 0xa80,/* Interrupts enabled config */ + SI_SUB_SMP = 0xa85,/* start the APs*/ SI_SUB_ROOT_CONF= 0xb00,/* Find root devices */ SI_SUB_DUMP_CONF= 0xb20,/* Find dump devices */ SI_SUB_RAID = 0xb38,/* Configure GEOM classes */ @@ -165,7 +166,6 @@ SI_SUB_KTHREAD_BUF = 0xea0,/* buffer daemon*/ SI_SUB_KTHREAD_UPDATE = 0xec0,/* update daemon*/ SI_SUB_KTHREAD_IDLE = 0xee0,/* idle procs*/ - SI_SUB_SMP = 0xf00,/* start the APs*/ SI_SUB_RACCTD = 0xf10,/* start racctd*/ SI_SUB_LAST = 0xfff /* final initialization */ }; Did you inspected all reordered sysinit routines and ensured that the reordering is safe ? At very least, SUB_SMP starts event timers, while KTHREAD_IDLE is about configuring some hardware which might be required/not ready for that. This fixes a problem for Mellanox drivers in the OFED layer. Possibly we need to move the SMP even earlier to not miss the generic FreeBSD PCI device enumeration or maybe this is not possible. Does anyone know how early we can start SMP? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Jenkins build is still unstable: FreeBSD_HEAD-tests2 #520
See https://jenkins.freebsd.org/job/FreeBSD_HEAD-tests2/520/ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [RFC] Start SMP subsystem earlier
On 5 January 2015 at 06:08, Hans Petter Selasky h...@selasky.org wrote: On 01/05/15 14:43, Konstantin Belousov wrote: On Mon, Jan 05, 2015 at 02:18:17PM +0100, Hans Petter Selasky wrote: Hi, There is a limitiation on the number of interrupt vectors available when only a single processor is running. To have more interrupts available we need to start SMP earlier when building a monotolith kernel and not loading drivers as modules. The driver in question is a network driver and because it cannot be started after SI_SUB_ROOT_CONF due to PXE support I see no other option than to move SI_SUB_SMP earlier. Suggested patch: Index: sys/kernel.h === --- sys/kernel.h(revision 276691) +++ sys/kernel.h(working copy) @@ -152,6 +152,7 @@ SI_SUB_KPROF= 0x900,/* kernel profiling*/ SI_SUB_KICK_SCHEDULER = 0xa00,/* start the timeout events*/ SI_SUB_INT_CONFIG_HOOKS = 0xa80,/* Interrupts enabled config */ + SI_SUB_SMP = 0xa85,/* start the APs*/ SI_SUB_ROOT_CONF= 0xb00,/* Find root devices */ SI_SUB_DUMP_CONF= 0xb20,/* Find dump devices */ SI_SUB_RAID = 0xb38,/* Configure GEOM classes */ @@ -165,7 +166,6 @@ SI_SUB_KTHREAD_BUF = 0xea0,/* buffer daemon*/ SI_SUB_KTHREAD_UPDATE = 0xec0,/* update daemon*/ SI_SUB_KTHREAD_IDLE = 0xee0,/* idle procs*/ - SI_SUB_SMP = 0xf00,/* start the APs*/ SI_SUB_RACCTD = 0xf10,/* start racctd*/ SI_SUB_LAST = 0xfff /* final initialization */ }; Did you inspected all reordered sysinit routines and ensured that the reordering is safe ? At very least, SUB_SMP starts event timers, while KTHREAD_IDLE is about configuring some hardware which might be required/not ready for that. Hi, I did not inspect everything myself yet regarding this change. That's why I'm sending this e-mail out. The problem is simply that the total number of interrupts appears to be limited by APIC_NUM_IOINTS and NUM_IO_INTS which is per CPU from what I understand. Until SMP is activated the newbus code is simply distributing the IRQ vectors on the available IRQs, then when SMP is up it is re-shuffling them all. I was initially thinking that a hack might be possible, like using RF_SHARED for the IRQ resource, but then noticed that we were using MSI interrupts, which are not allocated in the same manner. The other issue is that the IRQs should be functional too, so that PXE boot can work. I'm also starting to see increasing amounts of wifi hardware that expects interrupts to be up and working during probe/attach. (I think i915kms has the same issue too, no?) -adrian ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: vt and VirtualBox?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 01/05/2015 07:56, Lev Serebryakov wrote: Is here any possibility to add virtualbox driver to vt? Now console of -CURRENT guest in VirtualBox (using vga driver) is almost unusable slow! Sorry, we do not have KMS for VirtualBox guest yet. I'm not sure, that VirtualBox has API for paravirtualized screen output, though (guest addons?). Someone with copious free time and enough knowledge should be able to port Linux KMS/DRM2 driver for us. https://www.virtualbox.org/browser/vbox/trunk/src/VBox/Additions/linux It shouldn't be too hard. ;-) Jung-uk Kim -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQEcBAEBCAAGBQJUqsXNAAoJEHyflib82/FGni4H/RJrYLCNoYKdny70LJ0O6+o0 Mh5sf/fdfUkmfynrbyDAgCFfXdzD2/3p2NIX4WGgysUxOTgtWGFTLW67VNnQupwK pBSwz7Ute4LrSmXgHiKeNsduYtiIsOTY6744iFnEeELRgcY+g/ZDGxa6+zH2YxVW 82wWvbkgQA6wWtJw9sPOTYn2SjXRC+TUUcZcIqhcFxSdnJwpMzJ0QFEzrWxwV7hy ip3fi5XLlGqiPrv6C67m0L+YgZPRfMe2vA1/nDvOqzdVari+72TnffcKx/xvVgEO ZqQRG2P61Itut8b8LDS2bLEQQRpBILFbe7mpdlcAaYoLhdHFGfjjEYvrYcAn9cI= =o1su -END PGP SIGNATURE- ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: vt and VirtualBox?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 05.01.2015 20:11, Jung-uk Kim wrote: Someone with copious free time and enough knowledge should be able to port Linux KMS/DRM2 driver for us. https://www.virtualbox.org/browser/vbox/trunk/src/VBox/Additions/linux It shouldn't be too hard. ;-) This driver looks empty to me :) On the other hand here is https://www.virtualbox.org/browser/vbox/trunk/src/VBox/Additions/freebsd/drm/ - -- // Lev Serebryakov AKA Black Lion -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (MingW32) iQJ8BAEBCgBmBQJUqsmJXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRGOTZEMUNBMEI1RjQzMThCNjc0QjMzMEFF QUIwM0M1OEJGREM0NzhGAAoJEOqwPFi/3EePfL0P+gJAtX5zpJAOL5xczPwPU5JL d6CFQMDOBAnbHk7RaBSuY4JIuvyLE/9xORSYgM4ll8t1Uhn8f33nFLNiD2kIbJsF ntMlYIS1axJubvSNBs+u1U08tEANlyxFMKEaVvzNQ8L0e3wx1MTjwNCJcN3kU9AY nUu1Twwn6YB5K1E6JJ0cICzmdgw3LAJOUjql8sZh6amyFwWk2xInV7Bxf8+DYG4S 2U1xRmmxxiEhtksPesnVsHe1u4I4gS36U15yjwycsyMLyaNEwUe412pyTGKAeeWZ iwCRpSQbmXb3uMsZbQcC8Xb5F1dsMMWgIqQl/4IWhDnyY4eaYNqMeNnDEYmXv5IR Qo/m3mzFoUEs8A0U7JyH3GOrSnGtHeEBdqs1t+aGbZfU4dfiDql8TLcV1Z7uKksq Sl0seAV29jPSB5YBazPsxVJkFsR25qv2TFOvYzGlwsfF39mJHsjZRIgz7cLWaLbM PU0E96EUn6cnL72bHJkaYKzs5ZOBa2ThvgXLo31Uqj4jbgR6kembT9iGId295pIb Lo9Tf2bJWzAvPoEwNulc4mMagUiUez6jSYez09+iN3km0c1/EkIMqDdfK5DXWiQN 2cYyUEDF+WInZwqW7Fa9Rq99xILrUNgv1ENs587Ixs5mOnDlInpvs7cLVlf5YsYj 2iecQhYsC6aYTneYV52s =6MF5 -END PGP SIGNATURE- ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: vt and VirtualBox?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 01/05/2015 12:27, Lev Serebryakov wrote: On 05.01.2015 20:11, Jung-uk Kim wrote: Someone with copious free time and enough knowledge should be able to port Linux KMS/DRM2 driver for us. https://www.virtualbox.org/browser/vbox/trunk/src/VBox/Additions/linux It shouldn't be too hard. ;-) This driver looks empty to me :) I meant: https://www.virtualbox.org/browser/vbox/trunk/src/VBox/Additions/linux/drm On the other hand here is https://www.virtualbox.org/browser/vbox/trunk/src/VBox/Additions/freebsd/drm/ This driver is UMS/DRM1. vt(4) cannot use this driver. Jung-uk Kim -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQEcBAEBCAAGBQJUqsrIAAoJEHyflib82/FGSWIH/3pS+JUOsVCJTV/jWle+3a0Y QXrCBOZCjL/dMH3r0ZRe3OvQWMwab396lMT+sSsQW59LjeVq7jf7H+nocIxHxoQr 82zkFUZazELkcjEwkguaYiGiIPgM6/HKq3wQQvGFA1Y/t8Hjs/LtEEcEjAksBeE3 bIYfLa5BWoNv+3WfVJeelbinACgp6W9V8oLZRnWzK1f6yiMfMaFwSbgGnEQuHRMz YWfL5RGlVA9Z9B7IxXN+HWvctP0cCXTpQ3uyQJ+/TFWnlFlVQs4DBYcqsJ+B1QPV MZAlVTTQgiHF7tn6LIm5E6Su7647szDF3fNCnvc/8g4bHqVDl4JMEGLWH4W/dxU= =X78W -END PGP SIGNATURE- ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Haswell CPU Feature
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 01/05/15 16:57, Neel Natu wrote: Congratulations, you have the ability to debug the Haswell silicon HA! Is this turned on purposefully (its a feature of the CPU) or is this turned on unintentionally and is a bug in manufacturing? sean -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQF8BAEBCgBmBQJUqzlLXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRCQUFENDYzMkU3MTIxREU4RDIwOTk3REQx MjAxRUZDQTFFNzI3RTY0AAoJEBIB78oecn5k3GUIAJIbfTFkgiz1yuMkTbJtXUGe e9orU4iOoULSBksHMSrT1FYr3LoK1XTBJtqBadOtLa9BU7VPLeaDELr1HoPK9dHr h3ps4qkG7yAen3bH6U2oo64UAkjjEBRaY82LgkuSMFCFq1Y96EzphL+O7AKzbGYJ VblMY/Yrm45NiG8l2TuniRyBoiLhkdeYcBSPR8ErTbxyiO3l6bCilz5dI/h8icoR gps0v+0f6Bk1O5LuO33ctgf1iZKdP+yckmk2NCYNoe6oXO2+f4Y9u8jhTXar+5ey B2pG0IWK/cqEk1/53c6I+/X85YL+YNw9D9fObxZapml6nb06FHmTiBlnLcWL/PM= =Civ3 -END PGP SIGNATURE- ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Haswell CPU Feature
On Tue, Jan 6, 2015 at 4:24 AM, Sean Bruno sbr...@ignoranthack.me wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 01/05/15 16:57, Neel Natu wrote: Congratulations, you have the ability to debug the Haswell silicon HA! Is this turned on purposefully (its a feature of the CPU) or is this turned on unintentionally and is a bug in manufacturing? sean My desktop i5-4570 contain this flag too Origin=GenuineIntel Id=0x306c3 Family=0x6 Model=0x3c Stepping=3 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0x7ffafbffSSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,SMX,EST,TM2,SSSE3,b11,FMA,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,TSCDLT,AESNI,XSAVE,OSXSAVE,AVX,F16C,RDRAND ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Haswell CPU Feature
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 \014b11 I don't know what this cpu feature2 flag means, but my x240 haswell laptop has a b11 feature2 set. sean dmesg | grep -i features Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0x7ffafbbfSSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,b11,FMA,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,TSCDLT,AESNI,XSAVE,OSXSAVE,AVX,F16C,RDRAND -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQF8BAEBCgBmBQJUqzBsXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRCQUFENDYzMkU3MTIxREU4RDIwOTk3REQx MjAxRUZDQTFFNzI3RTY0AAoJEBIB78oecn5ktYUH/A/2P6aNyBfBMhM7pRThx/DC kulQbmHCuqOFwzJnE8qI/1YTvItNFG2sAsspd0iT2FmC2oEY/z6+j2ba2UizMJmH +ppjseAzs4+GY2N6cxT0BHf1yNoMDqlwdeWVeSODCn2HCc9Cc9Wz0e0RUOpwQ4zx Hmm1zI0Rla1izMIm437Lv38RFP1q/KaNLailcwgYrjvd90RaqobDeE2If3BYe8uv qvYUeap3hRk0EOrjMRBuGyMSIGkssHa1NyfQFYEmzg3F9F8lgTnCBYlspovjacoy I+LRWBUpOGS89vBxCjnLuBZO9fFajSJ0b6X8K8Cw4QWZmefPZWutujgf5ObzBhI= =oXdb -END PGP SIGNATURE- ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Haswell CPU Feature
Hi Sean, On Mon, Jan 5, 2015 at 4:46 PM, Sean Bruno sbr...@ignoranthack.me wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 \014b11 I don't know what this cpu feature2 flag means, but my x240 haswell laptop has a b11 feature2 set. sean dmesg | grep -i features Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0x7ffafbbfSSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,b11,FMA,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,TSCDLT,AESNI,XSAVE,OSXSAVE,AVX,F16C,RDRAND Congratulations, you have the ability to debug the Haswell silicon :-) From the Intel SDM, Table 3-20. Feature Information Returned in the ECX Register 11 | SDBG | A value of 1 indicates the processor supports IA32_DEBUG_INTERFACE MSR for silicon debug. best Neel -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQF8BAEBCgBmBQJUqzBsXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRCQUFENDYzMkU3MTIxREU4RDIwOTk3REQx MjAxRUZDQTFFNzI3RTY0AAoJEBIB78oecn5ktYUH/A/2P6aNyBfBMhM7pRThx/DC kulQbmHCuqOFwzJnE8qI/1YTvItNFG2sAsspd0iT2FmC2oEY/z6+j2ba2UizMJmH +ppjseAzs4+GY2N6cxT0BHf1yNoMDqlwdeWVeSODCn2HCc9Cc9Wz0e0RUOpwQ4zx Hmm1zI0Rla1izMIm437Lv38RFP1q/KaNLailcwgYrjvd90RaqobDeE2If3BYe8uv qvYUeap3hRk0EOrjMRBuGyMSIGkssHa1NyfQFYEmzg3F9F8lgTnCBYlspovjacoy I+LRWBUpOGS89vBxCjnLuBZO9fFajSJ0b6X8K8Cw4QWZmefPZWutujgf5ObzBhI= =oXdb -END PGP SIGNATURE- ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Haswell CPU Feature
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 01/05/15 17:50, Andrey Fesenko wrote: On Tue, Jan 6, 2015 at 4:24 AM, Sean Bruno sbr...@ignoranthack.me wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 01/05/15 16:57, Neel Natu wrote: Congratulations, you have the ability to debug the Haswell silicon HA! Is this turned on purposefully (its a feature of the CPU) or is this turned on unintentionally and is a bug in manufacturing? sean My desktop i5-4570 contain this flag too Origin=GenuineIntel Id=0x306c3 Family=0x6 Model=0x3c Stepping=3 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0x7ffafbffSSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,SMX,EST,TM2,SSSE3,b11,FMA,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,TSCDLT,AESNI,XSAVE,OSXSAVE,AVX,F16C,RDRAND I'm thinking something like this: Index: sys/x86/x86/identcpu.c === - --- sys/x86/x86/identcpu.c(revision 276729) +++ sys/x86/x86/identcpu.c (working copy) @@ -781,7 +781,7 @@ \011TM2 /* Thermal Monitor 2 */ \012SSSE3 /* SSSE3 */ \013CNXT-ID /* L1 context ID available */ - - \014b11 + \014SDBG /* IA32_DEBUG_INTERFACE debug*/ \015FMA /* Fused Multiply Add */ \016CX16 /* CMPXCHG16B Instruction */ \017xTPR /* Send Task Priority Messages*/ sean -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQF8BAEBCgBmBQJUq0m+XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRCQUFENDYzMkU3MTIxREU4RDIwOTk3REQx MjAxRUZDQTFFNzI3RTY0AAoJEBIB78oecn5kigkIAI2Naiv2TENl+1SFAQ5oHTUu HR+sbz3o7p71W8/9WhdkiMhHLwpF5ZGrpqh9Jc4CYuyNax4OvzD9du8b1RFVVBtx AR6K+zFE1/wHC8S+iEB2QsWLWjd6Y0NbZL1MvgEQTybFwLzdtEXafOi2gSsa2lK0 RFMd0VbE2xn2q9mp5GuTnR8fvqWGPSJLEtWTpEZri8vFnBIMC+kocb//kOhY6JsF SNcpJ2RfhXiQyOOZT/ETe47s7A29R9VW5u/+Hg8VnNuq5rV5o2PXa68VvSmAu4gr IxPMoodFUITXTpS/lfmkOf4W+uTSqUji+Y/u1yjNzS4MgodoEh6mc7gDuH9Xoj0= =j1kZ -END PGP SIGNATURE- ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Haswell CPU Feature
On Tue, Jan 6, 2015 at 1:23 PM, Neel Natu neeln...@gmail.com wrote: Hi Sean, On Mon, Jan 5, 2015 at 6:34 PM, Sean Bruno sbr...@ignoranthack.me wrote: I'm thinking something like this: Index: sys/x86/x86/identcpu.c === - --- sys/x86/x86/identcpu.c(revision 276729) +++ sys/x86/x86/identcpu.c (working copy) @@ -781,7 +781,7 @@ \011TM2 /* Thermal Monitor 2 */ \012SSSE3 /* SSSE3 */ \013CNXT-ID /* L1 context ID available */ - - \014b11 + \014SDBG /* IA32_DEBUG_INTERFACE debug*/ \015FMA /* Fused Multiply Add */ \016CX16 /* CMPXCHG16B Instruction */ \017xTPR /* Send Task Priority Messages*/ Looks good. Maybe also this for completeness? # svnlite diff Index: sys/x86/include/specialreg.h === --- sys/x86/include/specialreg.h(revision 276737) +++ sys/x86/include/specialreg.h(working copy) @@ -154,6 +154,7 @@ #defineCPUID2_TM2 0x0100 #defineCPUID2_SSSE30x0200 #defineCPUID2_CNXTID 0x0400 +#defineCPUID2_SDBG 0x0800 #defineCPUID2_FMA 0x1000 #defineCPUID2_CX16 0x2000 #defineCPUID2_XTPR 0x4000 -Jia-Shiun ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Haswell CPU Feature
Hi Sean, On Mon, Jan 5, 2015 at 6:34 PM, Sean Bruno sbr...@ignoranthack.me wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 01/05/15 17:50, Andrey Fesenko wrote: On Tue, Jan 6, 2015 at 4:24 AM, Sean Bruno sbr...@ignoranthack.me wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 01/05/15 16:57, Neel Natu wrote: Congratulations, you have the ability to debug the Haswell silicon HA! Is this turned on purposefully (its a feature of the CPU) or is this turned on unintentionally and is a bug in manufacturing? sean My desktop i5-4570 contain this flag too Origin=GenuineIntel Id=0x306c3 Family=0x6 Model=0x3c Stepping=3 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0x7ffafbffSSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,SMX,EST,TM2,SSSE3,b11,FMA,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,TSCDLT,AESNI,XSAVE,OSXSAVE,AVX,F16C,RDRAND I'm thinking something like this: Index: sys/x86/x86/identcpu.c === - --- sys/x86/x86/identcpu.c(revision 276729) +++ sys/x86/x86/identcpu.c (working copy) @@ -781,7 +781,7 @@ \011TM2 /* Thermal Monitor 2 */ \012SSSE3 /* SSSE3 */ \013CNXT-ID /* L1 context ID available */ - - \014b11 + \014SDBG /* IA32_DEBUG_INTERFACE debug*/ \015FMA /* Fused Multiply Add */ \016CX16 /* CMPXCHG16B Instruction */ \017xTPR /* Send Task Priority Messages*/ Looks good. best Neel sean -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQF8BAEBCgBmBQJUq0m+XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRCQUFENDYzMkU3MTIxREU4RDIwOTk3REQx MjAxRUZDQTFFNzI3RTY0AAoJEBIB78oecn5kigkIAI2Naiv2TENl+1SFAQ5oHTUu HR+sbz3o7p71W8/9WhdkiMhHLwpF5ZGrpqh9Jc4CYuyNax4OvzD9du8b1RFVVBtx AR6K+zFE1/wHC8S+iEB2QsWLWjd6Y0NbZL1MvgEQTybFwLzdtEXafOi2gSsa2lK0 RFMd0VbE2xn2q9mp5GuTnR8fvqWGPSJLEtWTpEZri8vFnBIMC+kocb//kOhY6JsF SNcpJ2RfhXiQyOOZT/ETe47s7A29R9VW5u/+Hg8VnNuq5rV5o2PXa68VvSmAu4gr IxPMoodFUITXTpS/lfmkOf4W+uTSqUji+Y/u1yjNzS4MgodoEh6mc7gDuH9Xoj0= =j1kZ -END PGP SIGNATURE- ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
false alarm (Re: invalid checksum with vtnet and in_kernel BOOTP)
for the records, this was not a problem with vtnet but a bug in some bhyve modifications of ours. Thanks to Bryan who pointed out the potential location of the problem. cheers luigi On Sat, Jan 03, 2015 at 08:00:22PM +0100, Luigi Rizzo wrote: I am trying to run a diskless bhyve client diskless using in-kernel bootp support and vtnet connected to tap and bridge on the host side and I am having the problem in the subject which may be vtnet-related. Packets generated by the in-kernel DHCP arrive to the host tap interface with a corrupt checksum, which is consistent with vtnet0 having the TXCSUM capability enabled. Unfortunately, when the packet reaches the bridge0 on the host: uname -a FreeBSD bsd9.casa 10.0-STABLE FreeBSD 10.0-STABLE #0 r269180: ifconfig bridge0 bridge0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 ether 02:01:85:b1:55:00 id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15 maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200 root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0 member: re0 flags=143LEARNING,DISCOVER,AUTOEDGE,AUTOPTP ifmaxaddr 0 port 1 priority 128 path cost 20 member: tap0 flags=143LEARNING,DISCOVER,AUTOEDGE,AUTOPTP ifmaxaddr 0 port 4 priority 128 path cost 55 The packet goes out with a broken checksum and the (external) dhcp server does not respond. When the guest is up, i can run dhclient on the same guest interface and packets exit with a correct checksum. Maybe dhclient generates correct packets ignoring the TXCSUM setting. In any case i applied a quick fix (disable TXCSUM in if_vtnet.c) and at least can get the dhcp request reach the router and get a response back. Also note that subsequent (tcp) traffic through the interface is reported on the host with a correct checksum, so i suspect that either the kernel-bootp code does not pass the correct checksum flags, or somehow it is sent to the device too early in the initialization process. any idea ? cheers luigi ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: vt and VirtualBox?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 01/05/2015 12:33, Jung-uk Kim wrote: On 01/05/2015 12:27, Lev Serebryakov wrote: On 05.01.2015 20:11, Jung-uk Kim wrote: Someone with copious free time and enough knowledge should be able to port Linux KMS/DRM2 driver for us. https://www.virtualbox.org/browser/vbox/trunk/src/VBox/Additions/linux It shouldn't be too hard. ;-) This driver looks empty to me :) I meant: https://www.virtualbox.org/browser/vbox/trunk/src/VBox/Additions/linux/drm I realized Linux KMS driver was removed by this commit. https://www.virtualbox.org/changeset/48364 Sorry, Jung-uk Kim ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
