From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/11] LTTng-core (basic tracing infrastructure) 0.5.108]
Date: Fri, 15 Sep 2006 21:25:51 +0100 [thread overview]
Message-ID: <1158351951.29932.130.camel@localhost.localdomain> (raw)
In-Reply-To: <20060915183432.GJ4577@redhat.com>
Ar Gwe, 2006-09-15 am 14:34 -0400, ysgrifennodd Frank Ch. Eigler:
> locations, but this is self-modifying code involving multiple
> instructions, and appears to be tricky on SMP/preempt boxes.
Can you explain more about why this is the case. I would have though
that it's the same with one instruction or 100 to the non SMP case. You
may never patch an instruction while another CPU may be executing that
path and there must be a synchronizing point for each CPU before it hits
the patched instruction. See the Intel and AMD chip errata documents.
Figuring out how long to patch is a more complicated problem but there
is extant code to compute the length of an x86 instruction.
Alan
prev parent reply other threads:[~2006-09-15 20:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-15 18:34 [PATCH 0/11] LTTng-core (basic tracing infrastructure) 0.5.108] Frank Ch. Eigler
2006-09-15 20:25 ` Alan Cox [this message]
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=1158351951.29932.130.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=fche@redhat.com \
--cc=linux-kernel@vger.kernel.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.