From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33)
	id 1CeUaj-00035H-3J
	for qemu-devel@nongnu.org; Wed, 15 Dec 2004 03:33:01 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33)
	id 1CeUah-000338-7L
	for qemu-devel@nongnu.org; Wed, 15 Dec 2004 03:32:59 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.33) id 1CeUag-00032W-MA
	for qemu-devel@nongnu.org; Wed, 15 Dec 2004 03:32:58 -0500
Received: from [64.233.184.204] (helo=wproxy.gmail.com)
	by monty-python.gnu.org with esmtp (Exim 4.34) id 1CeULc-0007Zo-Fo
	for qemu-devel@nongnu.org; Wed, 15 Dec 2004 03:17:24 -0500
Received: by wproxy.gmail.com with SMTP id 57so40708wri
	for <qemu-devel@nongnu.org>; Wed, 15 Dec 2004 00:17:23 -0800 (PST)
Message-ID: <da6318370412150017381bfcc2@mail.gmail.com>
Date: Wed, 15 Dec 2004 09:17:23 +0100
From: Piotras <piotras@gmail.com>
Subject: Re: [Qemu-devel] page fault during ins
In-Reply-To: <41BF5DBF.2050101@bellard.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
References: <da63183704121306524ea9ac3d@mail.gmail.com>
	<41BF5DBF.2050101@bellard.org>
Reply-To: Piotras <piotras@gmail.com>, 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: Fabrice Bellard <fabrice@bellard.org>, qemu-devel@nongnu.org

Do we have any device where iomem read changes device state? 
Wouldn't such hardware cause problems with speculative execution 
(memory reads) on some real CPUs? Or am I missing something?


Piotrek


On Tue, 14 Dec 2004 22:40:15 +0100, Fabrice Bellard <fabrice@bellard.org> wrote:
> Another issue could be problems with 'movsw': the CPU could verify that
> it can write before doing the read to avoid restarting problems when
> talking to memory mapped devices...
> 
> Fabrice.