Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
soc:2008:stefanha:journal:week10 [2008/07/30 12:05] stefanha |
soc:2008:stefanha:journal:week10 [2008/08/08 05:16] (current) stefanha |
||
|---|---|---|---|
| Line 21: | Line 21: | ||
| **Note gPXE hangs under KVM-70**, at least Debian's ''kvm-70+dfsg-1'' package. For some reason it enters an infinite loop (or is so slow I have not waited for it to finish) in ''arch/i386/prefix/unnrv2b.S'' ''decompress16''. The same command-line runs fine when "kvm" is replaced by "qemu" and the CPU registers are identical between KVM and QEMU before calling the function. I have not investigated further since gPXE loads successfully under KVM-72. | **Note gPXE hangs under KVM-70**, at least Debian's ''kvm-70+dfsg-1'' package. For some reason it enters an infinite loop (or is so slow I have not waited for it to finish) in ''arch/i386/prefix/unnrv2b.S'' ''decompress16''. The same command-line runs fine when "kvm" is replaced by "qemu" and the CPU registers are identical between KVM and QEMU before calling the function. I have not investigated further since gPXE loads successfully under KVM-72. | ||
| - | Next steps: | + | ==== Thur 31 Jul ==== |
| - | * [e820] Try inverting the hidden regions list to an "allowed" regions list. Do e820 mangling as the intersection between e820 regions and the "allowed" regions. | + | Commits: |
| - | * [virtio] Do we need a native gPXE virtio driver? | + | * [[http://git.etherboot.org/?p=people/stefanha/gpxe.git;a=commit;h=0cba7e4fca1fbb8113aff33a57b8ad84f05e6c00|[image] Make embedded images user accessible]] |
| - | * [GDB] Add sample GDB session to wiki and explain commands | + | |
| - | * [DMA] DMA pool API so drivers can reserve DMA buffers on ''open()''. | + | **Embedded images are now accessible from the gPXE shell**. Mcb30 suggested keeping embedded images loaded so that users can access them from the gPXE shell. This could be helpful for debugging or simply experimenting with gPXE. I'm not sure if the current patch will make it into mainline since it makes the "boot" command without arguments unusable - the primary embedded image is loaded, plus whatever the user loaded manually, and gPXE doesn't know which one you want to boot when no argument is given. |
| - | * [b44] Cleanup, testing, performance. | + | |
| - | * [shutdown] Remove gPXE allocated memory and free up PXE+UNDI, if necessary. | + | ==== Fri 1 Aug ==== |
| - | * [bzImage] Expand the heap size to the full 64K segment when loading a bzImage kernel with version 2.02 or higher. | + | **Debugging gPXE KVM issues** where we experience hangs. The problem has been narrowed down and seems to be related to interrupt dispatch. The ROM prefix code implements a timeout loop which hangs under KVM because the timer counter is not changing. Laurent Vivier is investigating this and has found that inserting ''nop'' instructions makes the problem go away. |
| - | * [GDB] Real-mode remote debugging. | + | |
| + | **It's time to work through my TODO list** instead of playing with new things that come along. I really want to get the b44 driver into mainline and have not spent the time needed to get the code ready. | ||
| + | |||
| + | ===== Next Week ===== | ||
| + | On to [[.:week11|Week 11]]. | ||
