All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Piotras <piotras@gmail.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] page fault during ins
Date: Thu, 23 Dec 2004 09:45:41 +0100	[thread overview]
Message-ID: <1103791541.29993.18.camel@gaston> (raw)
In-Reply-To: <da6318370412150017381bfcc2@mail.gmail.com>

On Wed, 2004-12-15 at 09:17 +0100, Piotras wrote:
> 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?

This is still quit common unfortunately...

On archs like ppc, this is why IO space is marked "Guarded" to prevent
speculation.

Ben.

  parent reply	other threads:[~2004-12-23  9:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-13 14:52 [Qemu-devel] page fault during ins Piotras
2004-12-14 21:40 ` Fabrice Bellard
2004-12-14 22:29   ` malc
2004-12-15  8:17   ` Piotras
2004-12-17  0:07     ` Mark Williamson
2004-12-23  8:45     ` Benjamin Herrenschmidt [this message]
2004-12-15  8:22   ` Piotras
  -- strict thread matches above, loose matches on Subject: below --
2004-12-15 18:36 Juergen Keil
2004-12-15 20:07 ` Piotras

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=1103791541.29993.18.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=piotras@gmail.com \
    --cc=qemu-devel@nongnu.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.