All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jes Sorensen <jes@sgi.com>
To: kvm-ia64@vger.kernel.org
Subject: Re: [patch] fold struct vcpu_info into CPUState
Date: Mon, 27 Oct 2008 09:48:16 +0000	[thread overview]
Message-ID: <49058E60.6080507@sgi.com> (raw)
In-Reply-To: <48E0F318.7050303@sgi.com>

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?

Thanks,
Jes

WARNING: multiple messages have this Message-ID (diff)
From: Jes Sorensen <jes@sgi.com>
To: Hollis Blanchard <hollisb@us.ibm.com>
Cc: Glauber Costa <glommer@gmail.com>,
	kvm@vger.kernel.org, kvm-ia64@vger.kernel.org
Subject: Re: [patch] fold struct vcpu_info into CPUState
Date: Mon, 27 Oct 2008 10:48:16 +0100	[thread overview]
Message-ID: <49058E60.6080507@sgi.com> (raw)
In-Reply-To: <1224875457.9634.63.camel@localhost.localdomain>

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?

Thanks,
Jes

  parent reply	other threads:[~2008-10-27  9:48 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-29 15:24 [patch] fold struct vcpu_info into CPUState Jes Sorensen
2008-09-29 15:24 ` Jes Sorensen
2008-10-05 10:02 ` Avi Kivity
2008-10-05 10:02   ` Avi Kivity
2008-10-05 20:48 ` Glauber Costa
2008-10-05 20:48   ` Glauber Costa
2008-10-13 22:24 ` Glauber Costa
2008-10-13 22:24   ` Glauber Costa
2008-10-17 15:28 ` Jes Sorensen
2008-10-17 15:28   ` Jes Sorensen
2008-10-17 21:27 ` Glauber Costa
2008-10-17 21:27   ` Glauber Costa
2008-10-24 15:57 ` Jes Sorensen
2008-10-24 15:57   ` Jes Sorensen
2008-10-24 19:10 ` Hollis Blanchard
2008-10-24 19:10   ` Hollis Blanchard
2008-10-27  9:48 ` Jes Sorensen [this message]
2008-10-27  9:48   ` Jes Sorensen
2008-10-27 16:02 ` Hollis Blanchard
2008-10-27 16:02   ` Hollis Blanchard
2008-10-27 16:06 ` Jes Sorensen
2008-10-27 16:06   ` Jes Sorensen
  -- strict thread matches above, loose matches on Subject: below --
2008-10-28 16:25 [patch] v4 - " Jes Sorensen
2008-10-28 16:25 ` Jes Sorensen
2008-10-29 13:01 ` Anthony Liguori
2008-10-29 13:01   ` Anthony Liguori
2008-10-29 13:04 ` Jes Sorensen
2008-10-29 13:04   ` Jes Sorensen
2008-10-29 13:09 ` Anthony Liguori
2008-10-29 13:09   ` Anthony Liguori

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49058E60.6080507@sgi.com \
    --to=jes@sgi.com \
    --cc=kvm-ia64@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.