RE: VMWare Workstation 6 for debugging Linux Kernel (!)
Hi roland, It's really an interesting feature, IMHO, maybe the UML would be no more needed. thanks very much;-) Regards, 2007/4/20, roland <[EMAIL PROTECTED]>: Hi ! I think this one is damn interestig for linux kernel development: link: http://stackframe.blogspot.com/ contents: see below regards roland ps: i`m not directly related to vmware - so this is no advertisement! Tuesday, April 17, 2007 Debugging Linux kernels with Workstation 6.0 We just quietly added an exciting feature to Workstation 6.0. I believe it will make WS6 a great tool for Linux kernel development. You can now debug kernel of Linux VM with gdb running on the Host without changing anything in the Guest VM. No kdb, no recompiling and no need for second machine. All you need is a single line in VM's configuration file. To use the new feature, grab the latest build of WS6 here: http://www.vmware.com/products/beta/ws/ Put this line into configuration file of your Linux VM: debugStub.listen.guest32=1 Now whenever you run the virtual machine, you'll see the following on the Host console: VMware Workstation is listening for debug connection on port 8832. Run gdb on the Host, reference it to the kernel with symbols and attach to the virtual machine: % gdb (gdb) file vmlinux-2.4.21-27.EL.debug (gdb) target remote localhost:8832 That's it. The VM is blocked now, so you can "continue" it and "^C" back to gdb. Breakpoints, single step, memory inspection - all this works as usual. If you have SMP VM, then each VCPU is mapped on a thread, so use "info threads" and "thread NN" to switch between them. The kernels with symbols are sadly lacking on most distributions, but if you use RHEL then this website may help (look for kernel-debuginfo rpm): http://people.redhat.com/duffy/debuginfo/index-js.html The gdb support in WS6 is experimental, so there may be rough edges here and there. Please post on community forums if something doesn't work right or if you have a suggestion: http://www.vmware.com/community/ There are more debugging specific features in WS6 (for example, you can use gdb hand-in-hand with Record/Replay!). I will describe them shortly. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
RE: VMWare Workstation 6 for debugging Linux Kernel (!)
Hi roland, It's really an interesting feature, IMHO, maybe the UML would be no more needed. thanks very much;-) Regards, 2007/4/20, roland [EMAIL PROTECTED]: Hi ! I think this one is damn interestig for linux kernel development: link: http://stackframe.blogspot.com/ contents: see below regards roland ps: i`m not directly related to vmware - so this is no advertisement! Tuesday, April 17, 2007 Debugging Linux kernels with Workstation 6.0 We just quietly added an exciting feature to Workstation 6.0. I believe it will make WS6 a great tool for Linux kernel development. You can now debug kernel of Linux VM with gdb running on the Host without changing anything in the Guest VM. No kdb, no recompiling and no need for second machine. All you need is a single line in VM's configuration file. To use the new feature, grab the latest build of WS6 here: http://www.vmware.com/products/beta/ws/ Put this line into configuration file of your Linux VM: debugStub.listen.guest32=1 Now whenever you run the virtual machine, you'll see the following on the Host console: VMware Workstation is listening for debug connection on port 8832. Run gdb on the Host, reference it to the kernel with symbols and attach to the virtual machine: % gdb (gdb) file vmlinux-2.4.21-27.EL.debug (gdb) target remote localhost:8832 That's it. The VM is blocked now, so you can continue it and ^C back to gdb. Breakpoints, single step, memory inspection - all this works as usual. If you have SMP VM, then each VCPU is mapped on a thread, so use info threads and thread NN to switch between them. The kernels with symbols are sadly lacking on most distributions, but if you use RHEL then this website may help (look for kernel-debuginfo rpm): http://people.redhat.com/duffy/debuginfo/index-js.html The gdb support in WS6 is experimental, so there may be rough edges here and there. Please post on community forums if something doesn't work right or if you have a suggestion: http://www.vmware.com/community/ There are more debugging specific features in WS6 (for example, you can use gdb hand-in-hand with Record/Replay!). I will describe them shortly. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
RE: Question: removal of syscall macros?
2006/12/14, Teunis Peters <[EMAIL PROTECTED]>: Now that syscall macros have been pulled from the -mm tree, what method is recommended to use syscalls? (I've wasted a day grubbing through sources before giving up and copying the old syscall macros into one key driver) _syscall macros are used by: ATI driver (no choice. I'm working with laptops) I have the same problem as yours. Do you have any idea to use ATI firegl driver in recent kernels ? Thanks in advance. Regards, albcamus - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
RE: Question: removal of syscall macros?
2006/12/14, Teunis Peters [EMAIL PROTECTED]: Now that syscall macros have been pulled from the -mm tree, what method is recommended to use syscalls? (I've wasted a day grubbing through sources before giving up and copying the old syscall macros into one key driver) _syscall macros are used by: ATI driver (no choice. I'm working with laptops) I have the same problem as yours. Do you have any idea to use ATI firegl driver in recent kernels ? Thanks in advance. Regards, albcamus - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
RE: Linux v2.6.20-rc5
I guess that it is because 'paravirt_ops' was exported as GPL symbol, whereas
the vmware module doen't declare any license.
I tried to add the following line:
MODULE_LICENSE("GPL");
into vmmon.tar and vmnet.tar under /usr/lib/vmare/modules/source/,
then it works.
(but maybe will tear the copyright by VMWare Inc.)
my kernel: 2.6.21-rc3 with CONFIG_PARAVIRT=y
2007/1/14, Jeff Chua <[EMAIL PROTECTED]>:
I recompiled the vmmon module under the new kernel with
CONFIG_PARAVIRT=y. It compiled fine, but when loaded, it gives the
unknown symbol warning. I shalll make it clear that this is not a
kernel issue ... it's just vmware, but I don't know how to fix it, and
needed help from the experts.
Thanks,
Jeff.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
RE: Linux v2.6.20-rc5
I guess that it is because 'paravirt_ops' was exported as GPL symbol, whereas the vmware module doen't declare any license. I tried to add the following line: MODULE_LICENSE(GPL); into vmmon.tar and vmnet.tar under /usr/lib/vmare/modules/source/, then it works. (but maybe will tear the copyright by VMWare Inc.) my kernel: 2.6.21-rc3 with CONFIG_PARAVIRT=y 2007/1/14, Jeff Chua [EMAIL PROTECTED]: I recompiled the vmmon module under the new kernel with CONFIG_PARAVIRT=y. It compiled fine, but when loaded, it gives the unknown symbol warning. I shalll make it clear that this is not a kernel issue ... it's just vmware, but I don't know how to fix it, and needed help from the experts. Thanks, Jeff. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
RE: Question: schedule()
your kthread IS preemptible unless you call preempt_disable or some locking functions explicitly . Regards, albcamus 2007/3/6, Mockern <[EMAIL PROTECTED]>: Hi, What does schedule() function do? I want to make my kthread preemptive. Thanks - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
RE: Question: schedule()
your kthread IS preemptible unless you call preempt_disable or some locking functions explicitly . Regards, albcamus 2007/3/6, Mockern [EMAIL PROTECTED]: Hi, What does schedule() function do? I want to make my kthread preemptive. Thanks - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Why can't I build a running Kernel?
2007/2/12, Jiri Slaby <[EMAIL PROTECTED]>: Config seems to be fine. Please post lspci -vvvxx Attached. and lines from your boot loader. title Fedora Core (2.6.20) root (hd0,1) kernel /vmlinuz-2.6.20 ro root=LABEL=/ vga=0x31B initrd /initrd-2.6.20.img And I have the SATA device /dev/sda3 labeled as '/'. regards, -- Thanks and regards, albcamus<[EMAIL PROTECTED]> lspci_vvvxx.output Description: Binary data
Re: Why can't I build a running Kernel?
2007/2/12, Jiri Slaby [EMAIL PROTECTED]: Config seems to be fine. Please post lspci -vvvxx Attached. and lines from your boot loader. title Fedora Core (2.6.20) root (hd0,1) kernel /vmlinuz-2.6.20 ro root=LABEL=/ vga=0x31B initrd /initrd-2.6.20.img And I have the SATA device /dev/sda3 labeled as '/'. regards, -- Thanks and regards, albcamus[EMAIL PROTECTED] lspci_vvvxx.output Description: Binary data
