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/31 01:17] stefanha |
soc:2008:stefanha:journal:week10 [2008/08/08 05:16] (current) stefanha |
||
|---|---|---|---|
| Line 27: | Line 27: | ||
| **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. | **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. | ||
| - | Next steps: | + | ==== Fri 1 Aug ==== |
| - | * [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. | + | **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. |
| - | * [virtio] Do we need a native gPXE virtio driver? | + | |
| - | * [GDB] Add sample GDB session to wiki and explain commands | + | **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. |
| - | * [DMA] DMA pool API so drivers can reserve DMA buffers on ''open()''. | + | |
| - | * [b44] Cleanup, testing, performance. | + | ===== Next Week ===== |
| - | * [shutdown] Remove gPXE allocated memory and free up PXE+UNDI, if necessary. | + | On to [[.:week11|Week 11]]. |
| - | * [bzImage] Expand the heap size to the full 64K segment when loading a bzImage kernel with version 2.02 or higher. | + | |
| - | * [GDB] Real-mode remote debugging. | + | |
