Date: Thu, 5 Nov 2009 17:35:16 +0100 From: Giovanni Trematerra <giovanni.trematerra@gmail.com> To: Attilio Rao <attilio@freebsd.org> Cc: Kostik Belousov <kostikbel@gmail.com>, des@des.no, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: [PATCH] AMD Opteron Rev. E hack Message-ID: <4e6cba830911050835uc04023ds91fef552788dfe73@mail.gmail.com> In-Reply-To: <3bbf2fe10911050610p7d3bb0f4kb4446ea651aa7c93@mail.gmail.com> References: <4e6cba830911050302k56bed35aj5ca9fa16379ab325@mail.gmail.com> <20091105112834.GR2331@deviant.kiev.zoral.com.ua> <4e6cba830911050424y17ea8e7fmf5573b3a765eac27@mail.gmail.com> <20091105124505.GT2331@deviant.kiev.zoral.com.ua> <3bbf2fe10911050610p7d3bb0f4kb4446ea651aa7c93@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Nov 5, 2009 at 3:10 PM, Attilio Rao <attilio@freebsd.org> wrote: > > The good way to fix this is to offer an lfence on acq barriers and > leave the other cases untouched, but this could be meaning > re-structure out atomic.h a lot. I will try to think to a good way to > do that when I have more available time. > In the while the WARNING msg will do its job (I can still trimm the > URL path however). > Well, That's not so easy to fix as I thought. Thanks Attilio to point me out. -- Gianni
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4e6cba830911050835uc04023ds91fef552788dfe73>