On the other hand I'm not sure that even with the timer patch and without network connections you can get a Linux guest to go 'idle enough' to drop completely out of queue; there's user space daemons that get periodically active and the like.
Aber sicher! Right now my biggest problem is kswapd that wants a wakeup call every second, and I would be interesting to hear if someone can explain why it is a smart way to implement memory management like this. If no work was done since the previous call of kswapd, it should be possible to predict what needs to be done. But even at once per second we drop from queue alright. Once this is gone, the 5-second interval for kswapd is the next one to address.
Rob
