I started looking at this patch set. Parts 1-9 applied ok, but part10 (entry.S) failed to apply because of recent changes to this file to fix the problems with warnings when trying to get locks with interrupts blocked. I thought this would be a good point to test the bisectability of this patch set and started a build with just parts 1-9 applied. The build was perfectly clean, but the kernel hung during boot (possibly when first trying to run user processes by the look of the last few messages on the console. The code with parts 1-9 applied still looks readable, but I think we may need some documentation later to help with maintainability. Perhaps even a tool that can check to make sure people don't add direct uses of instructions to .S files that need to be paravirtualized. I'm talking to some of the virtualization people here to see if they can help me set up a system so that I will be able to test out the non-native execution paths. -Tony -- To unsubscribe from this list: send the line "unsubscribe linux-ia64" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
![]() |