mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Mikael Pettersson <mikpe@csd.uu.se>
Cc: vamsi@in.ibm.com,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	richardj_moore@uk.ibm.com, grundym@us.ibm.com,
	vamsi_krishna@in.ibm.com, suparna <bsuparna@in.ibm.com>
Subject: Re: [rfc] [patch] kernel hooks
Date: 03 Oct 2002 14:01:41 +0100	[thread overview]
Message-ID: <1033650101.28022.10.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <15772.15056.287602.502467@kim.it.uu.se>

On Thu, 2002-10-03 at 13:40, Mikael Pettersson wrote:
> You just triggered Intel's "Unsynchronised Cross-Modifying Code
> Operations Can Cause Unexpected Instruction Execution Results"
> Erratum, which affects _every_ multiprocessor Intel P6 box.
> It's Pentium 3 Erratum E49 if you want to look it up; the other
> Intel P6s have it too, but with different numbers.
> 
> In short, the only safe way to do this sort of thing is to force
> all other processors to wait on a barrier first, then modify the
> code, then release the barrier.

You must also ensure that the code you are modifying isnt on an IRQ path
(if it is you must do spin locks and then be very careful about cross
cpu tlb deadlocks). Finally you have no choice but to ensure you never
use it on the NMI path


  reply	other threads:[~2002-10-03 12:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-03 12:26 Vamsi Krishna S .
2002-10-03 12:40 ` Mikael Pettersson
2002-10-03 13:01   ` Alan Cox [this message]
2002-10-03 13:32 Richard J Moore
2002-10-03 14:00 ` Alan Cox
2002-10-04  9:23 Richard J Moore

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=1033650101.28022.10.camel@irongate.swansea.linux.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=bsuparna@in.ibm.com \
    --cc=grundym@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikpe@csd.uu.se \
    --cc=richardj_moore@uk.ibm.com \
    --cc=vamsi@in.ibm.com \
    --cc=vamsi_krishna@in.ibm.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®