From: Jeff D. <jd...@ka...> - 2000-12-09 21:57:17
|
ka...@ca... said: > tracing thread pid = 320 Linux version 2.4.0-test12-1um (administrator@xena) (gcc version 2.95.2-5 19991024 (cygwin experimental)) #159 Sat Dec 9 21:43:37 2000 Heh. Very cool. > fixed printk() to print (well, console_drivers is NULL for some > reason) That's because the console driver hasn't been initialized. printk stores up the stuff and dumps it out when console_init gets called. Jeff |
From: Jeff D. <jd...@ka...> - 2000-12-10 01:18:23
|
ka...@ca... said: > I need to know why we need setitimer, so can find the Win32 > alternative for it. That's the clock. The kernel won't work too well without a clock. The immediate place that you're going to need it is during the delay loop calibration. There needs to be a SIGVTALRM firing HZ times a second at that point. > The problem is that it doesn't compile if I don't defined the > __setup_start and __setup_end manually (although the are defined in > the ld script I use), so that checksetup() could successfully enumrate > them. How do you define them? > When I defined them, checksetup() seems to be enumrating 6 > zeroed kernel_param structs. So root_dev_setup isn't get called, as a > result. Any idea? Are there 6 __setups in the kernel? I would become familiar with objdump and use it to figure out what's in that section of the binary and what's not. Also locate what's not there, and that might give you some clues as to what's going on. Jeff |
From: Dan A. <ka...@ca...> - 2000-12-10 11:43:17
|
On Sat, 9 Dec 2000, Jeff Dike wrote: Found the problem with __setup. It was another mismatched symbol naming thing, like with csum_partial. Can UML work without POSIX signals? signal support is currently partially broken under cygwin (one main reason is that Windows doesn't really support POSIX signals). set_signals() tends to fail right now causing the kernel to exit. -- Dan Aloni da...@ka... |
From: Dan A. <ka...@ca...> - 2000-12-09 23:00:12
|
On Sat, 9 Dec 2000, Jeff Dike wrote: > ka...@ca... said: > > tracing thread pid = 320 Linux version 2.4.0-test12-1um (administrator@xena) (gcc version 2.95.2-5 19991024 (cygwin experimental)) #159 Sat Dec 9 21:43:37 2000 > > Heh. Very cool. > > > fixed printk() to print (well, console_drivers is NULL for some > > reason) > > That's because the console driver hasn't been initialized. printk stores up > the stuff and dumps it out when console_init gets called. I have a problem with the __setup mechanism used in the kernel. The ld script along with the __setup macro supposes to create a section in the executable with a bunch of kernel_param structs that were defined throughout the kernel by using __setup, so that various modules could insert their own kernel params without changing any kernel code. The problem is that it doesn't compile if I don't defined the __setup_start and __setup_end manually (although the are defined in the ld script I use), so that checksetup() could successfully enumrate them. When I defined them, checksetup() seems to be enumrating 6 zeroed kernel_param structs. So root_dev_setup isn't get called, as a result. Any idea? -- Dan Aloni da...@ka... |