Date: Mon, 22 Jan 2007 14:44:33 +0000
From: Alan <alan@lxorguk.ukuu.org.uk>
To: "Wink Saville" <wink@saville.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] Asynchronous Messaging
Message-ID: <20070122144433.68598359@localhost.localdomain>
In-Reply-To: <d4cf37a60701220019h7cae91f6nc33bd24761a54c67@mail.gmail.com>
References: <d4cf37a60701220019h7cae91f6nc33bd24761a54c67@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 823
Lines: 19

> This is accomplished by allocating a page (or more) of memory which
> is executable and mapped into every threads address space. Also, all
> ISR entry points are modified to detect if the code that was interrupted
> was executing within the ACE page. If it was then the ACE code is
> allowed to complete before the ISR continues. This then provides
> the guarantee of atomic execution.

What if you enter the ISR, pass the point of the check and then another
CPU core hits the ACE space ?

Also how do you handle the case where the code gets stuck in your atomic
pages ?

Alan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/