From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1NKhki-0001Mz-Cg
	for qemu-devel@nongnu.org; Tue, 15 Dec 2009 19:28:28 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1NKhkd-0001Kb-4J
	for qemu-devel@nongnu.org; Tue, 15 Dec 2009 19:28:27 -0500
Received: from [199.232.76.173] (port=33897 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1NKhkd-0001KS-1N
	for qemu-devel@nongnu.org; Tue, 15 Dec 2009 19:28:23 -0500
Received: from mail-px0-f189.google.com ([209.85.216.189]:48448)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <geleman@gmail.com>) id 1NKhkc-0000ga-Mj
	for qemu-devel@nongnu.org; Tue, 15 Dec 2009 19:28:22 -0500
Received: by pxi27 with SMTP id 27so284506pxi.4
	for <qemu-devel@nongnu.org>; Tue, 15 Dec 2009 16:28:21 -0800 (PST)
MIME-Version: 1.0
In-Reply-To: <4B2819E2.7050603@web.de>
References: <4B2620E3.2050604@siemens.com>
	<a38b25540912141807s16ff3625me02a74422bbfeb02@mail.gmail.com>
	<4B2819E2.7050603@web.de>
Date: Wed, 16 Dec 2009 08:28:21 +0800
Message-ID: <a38b25540912151628j4ac89851u22fed158c859af98@mail.gmail.com>
From: TeLeMan <geleman@gmail.com>
Content-Type: text/plain; charset=UTF-8
Subject: [Qemu-devel] Re: [FOR 0.12][PATCH] target-i386: Fix evaluation of
	DR7 register
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: Anthony Liguori <aliguori@us.ibm.com>, qemu-devel <qemu-devel@nongnu.org>

> Now to the content: env already equals single_cpu_env, so there is no
> need in writing it back. That's because break/watchpoints are triggered
> synchronously over the context in which they may raise an exception as
> result.
env in op_help.c is asm(AREG0) not single_cpu_env.
Did you test your codes?