Re: [patch] pass opague CPUState through libkvm instead of int vcpu

Avi Kivity wrote:
> Jes Sorensen wrote:
> It's good; applied, thanks.
> 
> There's a slight redundancy in that some callbacks are passed two 
> opaques (per-cpu and per-vm), but it won't kill anyone.
> 
> (btw, this could have been done much more simply: declare a thread local 
> variable to hold the current env)

The thread local current env is coming in the vcpu_info merge patch :-)

Cheers,
Jes