From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=53619 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PWc5B-0008Bm-AU for qemu-devel@nongnu.org; Sat, 25 Dec 2010 16:55:22 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PWc59-0002Tz-6v for qemu-devel@nongnu.org; Sat, 25 Dec 2010 16:55:20 -0500 Received: from speedy.comstyle.com ([206.51.28.2]:11498 helo=mail.comstyle.com) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PWc58-0002Tu-RX for qemu-devel@nongnu.org; Sat, 25 Dec 2010 16:55:19 -0500 Received: from rox.home.comstyle.com (206-248-185-189.dsl.teksavvy.com [206.248.185.189]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: brad) by mail.comstyle.com (Postfix) with ESMTPSA id 6FB19984A7 for ; Sat, 25 Dec 2010 16:55:12 -0500 (EST) From: Brad Subject: Re: [Qemu-devel] i386 target bug with cmpxchg instruction handling Date: Sat, 25 Dec 2010 16:55:10 -0500 References: <20101225211637.GA13596@rox.home.comstyle.com> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <201012251655.11032.brad@comstyle.com> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org On Saturday 25 December 2010 16:42:14 malc wrote: > On Sat, 25 Dec 2010, Brad wrote: > > The following diff fixes a bug with the i386 targets cmpxhg instruction > > handling. I'm making an attempt to submit this upstream since OpenBSD > > currently has this in our port but it was originally from NetBSD's > > pkgsrc tree with QEMU. > > > > http://www.netbsd.org/cgi-bin/query-pr-single.pl?number=42158 > > > > https://bugs.launchpad.net/qemu/+bug/569760 > > Please see > http://www.mail-archive.com/qemu-devel@nongnu.org/msg41500.html Ok. I see. Oh well, I guess we'll keep this as a local patch for now. It's better than the situation with the current upstream code. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.