From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HgFZ9-0000Ew-NP for qemu-devel@nongnu.org; Tue, 24 Apr 2007 03:35:59 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HgFZ9-0000EW-5o for qemu-devel@nongnu.org; Tue, 24 Apr 2007 03:35:59 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HgFZ8-0000EK-08 for qemu-devel@nongnu.org; Tue, 24 Apr 2007 03:35:58 -0400 Received: from wr-out-0506.google.com ([64.233.184.235]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1HgFTc-0005Az-Tx for qemu-devel@nongnu.org; Tue, 24 Apr 2007 03:30:17 -0400 Received: by wr-out-0506.google.com with SMTP id i20so3353043wra for ; Tue, 24 Apr 2007 00:30:15 -0700 (PDT) Message-ID: Date: Tue, 24 Apr 2007 01:30:14 -0600 From: "Atif Hashmi" Subject: Re: [Qemu-devel] Re: Detecting an assembly instruction in QEMU In-Reply-To: <83a4d4ca0704220609m33ebfda7m825dab6d0992be28@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_1490_29499011.1177399814738" References: <83a4d4ca0704080713t596e4d83lbd1c495d92eda581@mail.gmail.com> <83a4d4ca0704081514v584660e4h8a36e5d1aee16d82@mail.gmail.com> <83a4d4ca0704170249l83c5d7bqe0b0f8cc8b5a4a58@mail.gmail.com> <83a4d4ca0704220609m33ebfda7m825dab6d0992be28@mail.gmail.com> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org ------=_Part_1490_29499011.1177399814738 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi Eduardo, I have finished implementing the implementing the roll-back functionality for transactional memory. There is one thing that I wanted to ask you. In order to roll-back, I need to log all the memory references. So that in that case when a transaction fails and roll-back occurs, memory state can also be rolled back. I will really apprecaite if you could direct me to the piece of code in QEMU for i386, where I can intercept the memory references. Thanks, Atif On 4/22/07, Eduardo Felipe wrote: > > Hi Atif, > > Your code seems quite ok to me. Just try including stored_eip inside the > DisasContext, otherwise you'll lose its value between calls to disas_insn > function. > > Also make sure that the instructions you are using as markers are not > executed elsewhere, as your compiler could generate them inside regular code > or they could already exist in your OS. > > Regards, > Eduardo > > ------=_Part_1490_29499011.1177399814738 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi Eduardo,

I have finished implementing the implementing the roll-back functionality for transactional memory. There is one thing that I wanted to ask you. In order to roll-back, I need to log all the memory references. So that in that case when a transaction fails and roll-back occurs, memory state can also be rolled back.

I will really apprecaite if you could direct me to the piece of code in QEMU for i386, where I can intercept the memory references.

Thanks,
Atif

On 4/22/07, Eduardo Felipe <edusaper@gmail.com> wrote:
Hi Atif,

Your code seems quite ok to me. Just try including stored_eip inside the DisasContext, otherwise you'll lose its value between calls to disas_insn function.

Also make sure that the instructions you are using as markers are not executed elsewhere, as your compiler could generate them inside regular code or they could already exist in your OS.

Regards,
Eduardo


------=_Part_1490_29499011.1177399814738--