Date: Thu, 5 Nov 2009 13:24:53 +0100 From: Giovanni Trematerra <giovanni.trematerra@gmail.com> To: Kostik Belousov <kostikbel@gmail.com> Cc: Attilio Rao <attilio@freebsd.org>, des@des.no, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: [PATCH] AMD Opteron Rev. E hack Message-ID: <4e6cba830911050424y17ea8e7fmf5573b3a765eac27@mail.gmail.com> In-Reply-To: <20091105112834.GR2331@deviant.kiev.zoral.com.ua> References: <4e6cba830911050302k56bed35aj5ca9fa16379ab325@mail.gmail.com> <20091105112834.GR2331@deviant.kiev.zoral.com.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Nov 5, 2009 at 12:28 PM, Kostik Belousov <kostikbel@gmail.com> wrote: > > Aren't atomic_readandclear need the same workaround ? > I understood that the bug manifests itself only when lock instruction is used. atomic_readandclear doesn't use lock. I think i386/linux/linux_support.s and amd64/linux32/linux32_support.s need the work-around too. > It would be much easier to read the patch if you generated it > with analog of "svn diff -x -p" for your VCS. > I'm sorry, I'll do my best next time. -- Giovanni Trematerra
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4e6cba830911050424y17ea8e7fmf5573b3a765eac27>