On 05/15/2011 11:33 AM, Xiao Guangrong wrote:
>
> These atomic ops are always called from within the spinlock, so we don't
need an atomic_t here.
>
> Sorry, I should have noticed this on the first version.
We read indirect_shadow_pages atomically on pte write path, that is allowed out
of mmu_lock
Reading is fine:
#define atomic_read(v) (*(volatile int *)&(v)->counter)
--
error compiling committee.c: too many arguments to function
--
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
