Re: [patch] fold struct vcpu_info into CPUState

Hollis Blanchard
2008-10-27T16:02:23Z

On Mon, 2008-10-27 at 10:48 +0100, Jes Sorensen wrote:
> Hollis Blanchard wrote:
> > It looks like qemu is actually switching threads when this happens...
> > I'm not sure what the current state is of qemu/KVM threads... I think we
> > have 1 thread per vcpu, plus 1 IO thread? If that's right, maybe
> > current_env isn't being initialized in the IO thread; I only see that
> > happening inside ap_main_loop(), which is the vcpu thread.
> >
>
> Hmmm, this is bizarre. If it was the IO thread dieing because of this
> I would expect the same to happen on ia64. Could you try and add a test
> in the code to find out which thread you are when you die, and maybe
> check for current_env being valid?

I tested in gdb, and I can confirm that a) current_env was initialized
in one thread, and then used in another, and b) current_env was NULL
(invalid) when it was used.

Are you using virtio on ia64?

--
Hollis Blanchard
IBM Linux Technology Center