On 09/07/2011 08:21 PM, Don Zickus wrote:
>
> How about, during NMI, save %rip to a per-cpu variable. Handle just
> one cause. If, on the next NMI, we hit the same %rip, assume
> back-to-back NMI has occured and now handle all causes.
I had a similar idea a couple of months ago while debugging a continuous
flow of back-to-back NMIs from a stress-test perf application and I
couldn't get it to work. But let me try it again, because it does make
sense as an optimization.
Great, thanks.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
