From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1Lmf3O-0003bu-VD
	for qemu-devel@nongnu.org; Wed, 25 Mar 2009 22:10:46 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1Lmf3K-0003W5-9B
	for qemu-devel@nongnu.org; Wed, 25 Mar 2009 22:10:46 -0400
Received: from [199.232.76.173] (port=38595 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1Lmf3K-0003Vx-5T
	for qemu-devel@nongnu.org; Wed, 25 Mar 2009 22:10:42 -0400
Received: from mx2.redhat.com ([66.187.237.31]:41359)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <mtosatti@redhat.com>) id 1Lmf3J-0004TI-KK
	for qemu-devel@nongnu.org; Wed, 25 Mar 2009 22:10:41 -0400
Date: Wed, 25 Mar 2009 23:10:26 -0300
From: Marcelo Tosatti <mtosatti@redhat.com>
Subject: Re: [Qemu-devel] [patch 06/10] qemu: per-cpu thread information
Message-ID: <20090326021026.GA6765@amt.cnet>
References: <20090325224714.853788328@amt.cnet>
	<20090325225439.131253411@amt.cnet>
	<5d6222a80903251835x61da12ebgf79f336a82492645@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5d6222a80903251835x61da12ebgf79f336a82492645@mail.gmail.com>
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Glauber Costa <glommer@gmail.com>
Cc: qemu-devel@nongnu.org

On Wed, Mar 25, 2009 at 10:35:04PM -0300, Glauber Costa wrote:
> On Wed, Mar 25, 2009 at 7:47 PM, Marcelo Tosatti <mtosatti@redhat.com> wrote:
> > Move per-cpu thread information to CPUState. Initialize through per-arch
> > cpu_init.
> 
> What prevents it to happen in common code?

To be accessed in non-cpu context, you mean? Or to be accessed from
linux-user context?