|
From: Maran P. <ma...@li...> - 2013-07-02 11:34:14
|
In case of s390x, both of the following facilities are provided by the architecture. But the completion guarantee provided by s390x in the form of constrained transactions seem to be not provided by other architectures. Since constrained transactions do not come with fall-back path, Julian's proposal 1 - jump to the fall back path on a transaction begin - will most probably not help to support constrained transactions on s390x. On 07/02/2013 01:57 AM, Peter Bergner wrote: >> Am 29.06.2013 01:06, schrieb Eliot Moss: >>> 2. At least on x86 and maybe on PPC some status bits indicating failure >> and its cause need to be set appropriately when going to the failure path. > That is true for PPC too. > > > On Mon, 2013-07-01 at 19:25 +0200, Josef Weidendorfer wrote: >> I would assume that there always is a flag for something like "resource >> overflow"? In the hope that the failure path does not retry the same >> transaction again. > On PPC, we have a bit in the TEXASR register that says whether the > transaction failure is persistent. If it is persistent, the failure > code should not retry the hardware transaction. > > Peter > > > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Windows: > > Build for Windows Store. > > http://p.sf.net/sfu/windows-dev2dev > _______________________________________________ > Valgrind-developers mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-developers > > |