ssh-keygen -Z
Hello, there is -Z parameter in ssh-keygen --help output, but no mention of it in ssh-keygen's man-page. Any clue what values this parameter accept? -- Regards, Ruslan T.O.S. Of Reality ___ 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: quick hack to support option VIMAGE on USB Ethernet
Hello, The problem of USB ethernet device with VIMAGE kernel still remains with 10.0-RELEASE and I think I have found the reason and a fix. I have filed a patch and backtrace as a followup to the PR http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/183835 I will repeat the explanation here. The problem occur when ue_attach_post_task() (in sys/dev/usb/net/usb_ethernet.c) is called. ue_attach_post_task() calls if_alloc() (in sys/net/if.c) and ether_attach() (in sys/net/if_ethersubr.c), which finally refer V_if_index. The problem is that curvnet is NULL when ue_attach_post_task() is invoked, and with VIMAGE, V_if_index is defined to VNET(if_index) = VNET_VNET(curvnet, if_index) = (*VNET_VNET_PTR((curvnet), if_index)) = (*_VNET_PTR((curvnet)-vnet_data_base, if_index)) and so on. For device attach, the following code in device_probe_and_attach() (in kern/subr_bus.c) CURVNET_SET_QUIET(vnet0); error = device_attach(dev); CURVNET_RESTORE(); should assign curvnet to vnet0, but it is not the case for ue device. As an example of USB ethernet device, with if_axe, device_attach(dev) is axe_attach() (in sys/dev/usb/net/if_axe.c). axe_attach() calls uether_ifattach() (in sys/dev/usb/net/usb_ethernet.c) (other USB ethernet devices' *_attach() also call this function), which *queues* (not calls) ue_attach_post_task(). As ue_attach_post_task is called from usb_process (not from uther_ifattach), it is not assured that curvnet is properly assigned. 2013-08-14 4:08 GMT+09:00 Craig Rodrigues rodr...@freebsd.org: On Mon, Aug 12, 2013 at 8:57 PM, YAMAMOTO Shigeru shig...@iij.ad.jp wrote: My try is, 1) I try to enable option VIMAGE at r254236@HEAD. It causes panic at accessing V_if_index in ifindex_alloc_locked(). Can you provide the kernel backtrace for this panic? It would be interesting to see where we need to initialize currvnet for USB Ethernet. I thought we already handled that case in subr_bus.c -- Craig ___ 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: quick hack to support option VIMAGE on USB Ethernet
Take a look at petitecloud.org it might solve your issue we have a working cloud on a stick for stuff like the above (using bhyve running off a usb drive) On Sun, Aug 11, 2013 at 11:48 PM, YAMAMOTO Shigeru shig...@iij.ad.jpwrote: Hi all, I hope to use option VIMAGE on RaspberryPi. So, I try to make a patch. http://freebsd-current.os-hackers.jp/pub/FreeBSD/snapshots/20130812/raspberry-pi/patch-vimage-r254236.diff #There is a SD image for RaspberryPi at same place. But, I only test it for if_smsc driver on RaspberryPi. I don't test other architectures/devices. Please test my patch and suggest the way to support option VIMAGE on USB devices, if you are interested in. Thanks, --- YAMAMOTO Shigeru shig...@iij.ad.jp ___ 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 -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.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: quick hack to support option VIMAGE on USB Ethernet
Forgot to mention that the actual solution is only in our mailing list archives but should in the next few days be on the site On Sun, Feb 16, 2014 at 5:29 AM, Aryeh Friedman aryeh.fried...@gmail.comwrote: Take a look at petitecloud.org it might solve your issue we have a working cloud on a stick for stuff like the above (using bhyve running off a usb drive) On Sun, Aug 11, 2013 at 11:48 PM, YAMAMOTO Shigeru shig...@iij.ad.jpwrote: Hi all, I hope to use option VIMAGE on RaspberryPi. So, I try to make a patch. http://freebsd-current.os-hackers.jp/pub/FreeBSD/snapshots/20130812/raspberry-pi/patch-vimage-r254236.diff #Therehttp://freebsd-current.os-hackers.jp/pub/FreeBSD/snapshots/20130812/raspberry-pi/patch-vimage-r254236.diff#Thereis a SD image for RaspberryPi at same place. But, I only test it for if_smsc driver on RaspberryPi. I don't test other architectures/devices. Please test my patch and suggest the way to support option VIMAGE on USB devices, if you are interested in. Thanks, --- YAMAMOTO Shigeru shig...@iij.ad.jp ___ 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 -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.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: quick hack to support option VIMAGE on USB Ethernet
16.02.2014 14:29, Aryeh Friedman пишет: Take a look at petitecloud.org it might solve your issue we have a working cloud on a stick for stuff like the above (using bhyve running off a usb drive) Is it only me who thinks that it's a pure SPAM? On Sun, Aug 11, 2013 at 11:48 PM, YAMAMOTO Shigeru shig...@iij.ad.jpwrote: I hope to use option VIMAGE on RaspberryPi. So, I try to make a patch. http://freebsd-current.os-hackers.jp/pub/FreeBSD/snapshots/20130812/raspberry-pi/patch-vimage-r254236.diff #There is a SD image for RaspberryPi at same place. But, I only test it for if_smsc driver on RaspberryPi. I don't test other architectures/devices. Please test my patch and suggest the way to support option VIMAGE on USB devices, if you are interested in. -- WBR, Boris Samorodov (bsam) FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ 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: quick hack to support option VIMAGE on USB Ethernet
16.02.2014 15:28, Aryeh Friedman пишет: He was asking how to run a VM on ARM something that one of our core team members has already demostrated and I was just giving a pointer to it (the archives are a little screw right now so no direct link) 1. Top quoting. 2. Unneeded over quoting. 3. Bogus quoting (my words were removed but name remained). 4. No technical answer at your first answer (only site link). 5. The aforementioned site does not have the word VIMAGE. This _is_ SPAM. PS. You claim to be a Lead Developer, so, please, try to write technical answers and to respect all others time (do appropriate quoting). On Sun, Feb 16, 2014 at 6:25 AM, Boris Samorodov b...@passap.ru wrote: 16.02.2014 14:29, Aryeh Friedman пишет: Take a look at petitecloud.org it might solve your issue we have a working cloud on a stick for stuff like the above (using bhyve running off a usb drive) Is it only me who thinks that it's a pure SPAM? On Sun, Aug 11, 2013 at 11:48 PM, YAMAMOTO Shigeru shig...@iij.ad.jp wrote: I hope to use option VIMAGE on RaspberryPi. So, I try to make a patch. http://freebsd-current.os-hackers.jp/pub/FreeBSD/snapshots/20130812/raspberry-pi/patch-vimage-r254236.diff #There is a SD image for RaspberryPi at same place. But, I only test it for if_smsc driver on RaspberryPi. I don't test other architectures/devices. Please test my patch and suggest the way to support option VIMAGE on USB devices, if you are interested in. -- WBR, Boris Samorodov (bsam) FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ 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: quick hack to support option VIMAGE on USB Ethernet
On Sun, 2014-02-16 at 06:28 -0500, Aryeh Friedman wrote: He was asking how to run a VM on ARM something that one of our core team members has already demostrated and I was just giving a pointer to it (the archives are a little screw right now so no direct link) What he was asking had nothing to do with running a VM on ARM. If you were actually a developer as you claim, you'd know that. Everything posted by this person so far is indeed off-topic spam. -- Ian On Sun, Feb 16, 2014 at 6:25 AM, Boris Samorodov b...@passap.ru wrote: 16.02.2014 14:29, Aryeh Friedman пишет: Take a look at petitecloud.org it might solve your issue we have a working cloud on a stick for stuff like the above (using bhyve running off a usb drive) Is it only me who thinks that it's a pure SPAM? On Sun, Aug 11, 2013 at 11:48 PM, YAMAMOTO Shigeru shig...@iij.ad.jp wrote: I hope to use option VIMAGE on RaspberryPi. So, I try to make a patch. http://freebsd-current.os-hackers.jp/pub/FreeBSD/snapshots/20130812/raspberry-pi/patch-vimage-r254236.diff #There is a SD image for RaspberryPi at same place. But, I only test it for if_smsc driver on RaspberryPi. I don't test other architectures/devices. Please test my patch and suggest the way to support option VIMAGE on USB devices, if you are interested in. -- WBR, Boris Samorodov (bsam) FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ 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 -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.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 ___ 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: M_FILEDESC leak
On 2/14/2014 10:12 PM, Bryan Drewery wrote: There's some leak of M_FILEDESC. Most head servers I look on have high filedesc usage in vmstat -m. Older (stable/9,8) do not. vmstat -m|grep filedesc usage on various servers: r259961 133350 (freefall) r261350 829256 (my dev server) r261411 67 (pointyhat) r263068 288122 (beefy1) r260368 1193324 (beefy2) I have figured this out and am preparing a patch for review/commit. This goes back at least to Jan 2013 in head, thus is in 10.0-R as well. -- Regards, Bryan Drewery signature.asc Description: OpenPGP digital signature
HEADS UP: Updated llvm/clang to 3.4 in r261991
Hi, I have just upgraded our copy of llvm/clang to 3.4 release, in r261991. This version supports all of the features in the current working draft of the upcoming C++ standard, provisionally named C++1y. The code generator's performance is greatly increased, and the loop auto-vectorizer is now enabled at -Os and -O2 in addition to -O3. The PowerPC backend has made several major improvements to code generation quality and compile time, and the X86, SPARC, ARM32, Aarch64 and SystemZ backends have all seen major feature work. Release notes for llvm and clang can be found here: http://llvm.org/releases/3.4/docs/ReleaseNotes.html http://llvm.org/releases/3.4/tools/clang/docs/ReleaseNotes.html Note that building lldb (using WITH_LLDB) will not work at this point, since our lldb snapshot was locally modified to be able to work with the old llvm 3.3 API. Ed Maste will most likely fix this very soon (and maybe import a new snapshot, I hope :-). Another important aspect for end-users and ports maintainers is the new compiler flag handling in clang 3.4. It has become more strict, in the sense that it will now error out on flags it does not recognize, in particular most gcc-specific optimization fine-tuning flags. Some ports which blindly use such gcc-specific flags will therefore be broken, but these are usually very easy to fix. During the exp-run which was done with this new version of clang, several ports with the highest number of dependent ports (open-motif, libtheora, boost-libs, etc) have already been handled, but more work still needs to be done. Last but not least, I hope we can now start using clang for more of our existing architectures, like powerpc, mips, and possibly even new ones like arm64. Enjoy! -Dimitry signature.asc Description: Message signed with OpenPGP using GPGMail
Re: HEADS UP: Updated llvm/clang to 3.4 in r261991
On Sun, 2014-02-16 at 21:06 +0100, Dimitry Andric wrote: Hi, I have just upgraded our copy of llvm/clang to 3.4 release, in r261991. This version supports all of the features in the current working draft of the upcoming C++ standard, provisionally named C++1y. The code generator's performance is greatly increased, and the loop auto-vectorizer is now enabled at -Os and -O2 in addition to -O3. The PowerPC backend has made several major improvements to code generation quality and compile time, and the X86, SPARC, ARM32, Aarch64 and SystemZ backends have all seen major feature work. Release notes for llvm and clang can be found here: http://llvm.org/releases/3.4/docs/ReleaseNotes.html http://llvm.org/releases/3.4/tools/clang/docs/ReleaseNotes.html Note that building lldb (using WITH_LLDB) will not work at this point, since our lldb snapshot was locally modified to be able to work with the old llvm 3.3 API. Ed Maste will most likely fix this very soon (and maybe import a new snapshot, I hope :-). Another important aspect for end-users and ports maintainers is the new compiler flag handling in clang 3.4. It has become more strict, in the sense that it will now error out on flags it does not recognize, in particular most gcc-specific optimization fine-tuning flags. Some ports which blindly use such gcc-specific flags will therefore be broken, but these are usually very easy to fix. During the exp-run which was done with this new version of clang, several ports with the highest number of dependent ports (open-motif, libtheora, boost-libs, etc) have already been handled, but more work still needs to be done. Last but not least, I hope we can now start using clang for more of our existing architectures, like powerpc, mips, and possibly even new ones like arm64. Enjoy! Is OpenMP supported in this version? Clang 3.4 from ports barfs: btw /usr/local/bin/clang34 -fopenmp /tmp/foo.c clang: warning: argument unused during compilation: '-fopenmp' Ditto the installed version of 3.3 under 10: btw clang -fopenmp /tmp/foo.c clang: warning: argument unused during compilation: '-fopenmp' -Dimitry ___ 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: HEADS UP: Updated llvm/clang to 3.4 in r261991
On 16 Feb 2014, at 21:16, Dennis Glatting free...@penx.com wrote: On Sun, 2014-02-16 at 21:06 +0100, Dimitry Andric wrote: I have just upgraded our copy of llvm/clang to 3.4 release, in r261991. This version supports all of the features in the current working draft of the upcoming C++ standard, provisionally named C++1y. ... Is OpenMP supported in this version? Clang 3.4 from ports barfs: No, this is still being worked on in trunk. Support from Intel was announced last August, here: http://lists.cs.uiuc.edu/pipermail/cfe-dev/2013-August/031595.html I hope it will be ready to appear in 3.5 release. There is currently an experimental version, based on clang 3.3, published here: http://clang-omp.github.io/ -Dimitry signature.asc Description: Message signed with OpenPGP using GPGMail
Re: M_FILEDESC leak
On 2/16/2014 12:35 PM, Bryan Drewery wrote: On 2/14/2014 10:12 PM, Bryan Drewery wrote: There's some leak of M_FILEDESC. Most head servers I look on have high filedesc usage in vmstat -m. Older (stable/9,8) do not. vmstat -m|grep filedesc usage on various servers: r259961 133350 (freefall) r261350 829256 (my dev server) r261411 67 (pointyhat) r263068 288122 (beefy1) r260368 1193324 (beefy2) I have figured this out and am preparing a patch for review/commit. This goes back at least to Jan 2013 in head, thus is in 10.0-R as well. Fixed in r262006. -- Regards, Bryan Drewery signature.asc Description: OpenPGP digital signature
Re: HEADS UP: Updated llvm/clang to 3.4 in r261991
On Sun, 2014-02-16 at 21:38 +0100, Dimitry Andric wrote: On 16 Feb 2014, at 21:16, Dennis Glatting free...@penx.com wrote: On Sun, 2014-02-16 at 21:06 +0100, Dimitry Andric wrote: I have just upgraded our copy of llvm/clang to 3.4 release, in r261991. This version supports all of the features in the current working draft of the upcoming C++ standard, provisionally named C++1y. ... Is OpenMP supported in this version? Clang 3.4 from ports barfs: No, this is still being worked on in trunk. Support from Intel was announced last August, here: http://lists.cs.uiuc.edu/pipermail/cfe-dev/2013-August/031595.html I hope it will be ready to appear in 3.5 release. There is currently an experimental version, based on clang 3.3, published here: http://clang-omp.github.io/ Thanks. I was confused between Phronix, the clang web site content, and trying to compile. -Dimitry ___ 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: ssh-keygen -Z
On Sun, 16 Feb 2014, Ruslan Makhmatkhanov wrote: Hello, there is -Z parameter in ssh-keygen --help output, but no mention of it in ssh-keygen's man-page. Any clue what values this parameter accept? It is the new-format ciphername, which can be used for RSA keys if the new format file is being used, and is used for the elliptic curve keys, if I'm reading things correctly. I guess that would mean that it accepts things like chacha20-poly1...@openssh.com and aes256-ctr (see the table ciphers[] in cipher.c), though I don't know which ones make sense to pass in there. I guess we should ask the OpenBSD folks to document it, the -Z argument was added to ssh-keygen.c in r1.237 back in December. -Ben ___ 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
