From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:36218) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Vq6ki-0001mQ-Q8 for qemu-devel@nongnu.org; Mon, 09 Dec 2013 14:44:30 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Vq6ka-00009s-Kj for qemu-devel@nongnu.org; Mon, 09 Dec 2013 14:44:24 -0500 Message-ID: <1386618244.5159.74.camel@pasglop> From: Benjamin Herrenschmidt Date: Tue, 10 Dec 2013 06:44:04 +1100 In-Reply-To: <52603062-FAEC-4D6C-8F56-112488CCBAA9@suse.de> References: <20131125153556.12615.63598.stgit@bahia.lab.toulouse-stg.fr.ibm.com> <52603062-FAEC-4D6C-8F56-112488CCBAA9@suse.de> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH] target-ppc: ppc64 target's virtio can be either endian. List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alexander Graf Cc: Rusty Russell , "qemu-ppc@nongnu.org list:PowerPC" , QEMU Developers On Mon, 2013-12-09 at 16:33 +0100, Alexander Graf wrote: > > Also can't virtio_get_byteswap pass in the CPU pointer of the CPU > that's calling in this moment? I'm not sure how racy it is to > synchronize the first cpu while we're not in the first cpu's execution > thread. The LPCR bit is always set on all CPUs. > Either way, if we do this "right" we don't even have to jump through > these hoops, as little endian setting simply happens steered from > QEMU, so QEMU will have all knowledge about the guest's little endian > mode without the need to synchronize any state. Ben.