On Wed, Mar 05, 2008 at 07:04:54AM +0100, Pierre Ossman wrote:Start: You discovered at some point where you currently have code a variable is not updated yet. Fact: You have some new code that runs before that point Information: The variable is updated later eventually in the idle exit path. Fact II: You require the variable to be updated in your new code Possible solutions: (1) you move your new code in a point of the idle exit path after the variable is updated (2) you move the code that updates the variable earlier before your code Solution: I described the first variant which is likely easier. How: I told you where it is updated, so that shouldn't be too difficult. Action: Implement solution (1) or (2) Action: Test if it works Check: If test succeeded exit Otherwise: Restart at Start -Andi --
| Andrew Morton | -mm merge plans for 2.6.23 |
| Chuck Ebbert | Why do so many machines need "noapic"? |
| Bart Van Assche | Integration of SCST in the mainstream Linux kernel |
| Greg Kroah-Hartman | [PATCH 023/196] MCP_UCB1200: Convert from class_device to device |
git: | |
| David Miller | Re: [BUG] New Kernel Bugs |
| Jarek Poplawski | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Gerrit Renker | [PATCH 31/37] dccp: Remove manual influence on NDP Count feature |
| Gregory Haskins | [RFC PATCH 00/17] virtual-bus |
