From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Hgkn4-0001tN-Ip for qemu-devel@nongnu.org; Wed, 25 Apr 2007 12:56:26 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Hgkn3-0001qS-19 for qemu-devel@nongnu.org; Wed, 25 Apr 2007 12:56:26 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Hgkn2-0001qH-Rf for qemu-devel@nongnu.org; Wed, 25 Apr 2007 12:56:24 -0400 Received: from nz-out-0506.google.com ([64.233.162.235]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1HgkhO-00028Q-JM for qemu-devel@nongnu.org; Wed, 25 Apr 2007 12:50:34 -0400 Received: by nz-out-0506.google.com with SMTP id i11so829457nzi for ; Wed, 25 Apr 2007 09:50:34 -0700 (PDT) Message-ID: Date: Wed, 25 Apr 2007 11:50:33 -0500 From: "Atif Hashmi" Subject: Re: [Qemu-devel] Re: Detecting an assembly instruction in QEMU In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_29268_7129340.1177519833537" References: <83a4d4ca0704081514v584660e4h8a36e5d1aee16d82@mail.gmail.com> <83a4d4ca0704170249l83c5d7bqe0b0f8cc8b5a4a58@mail.gmail.com> <83a4d4ca0704220609m33ebfda7m825dab6d0992be28@mail.gmail.com> <83a4d4ca0704240234q6f8ecf59gbfa91432a2fee08@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_29268_7129340.1177519833537 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi Eduardo, Thanks for pointing me to the file. Could you please clarify one more thing. Instructions like addl %ebx, (%eax) are also considered to be memory refernce instructions. Do these type of instructions also refer to the functions that you mentioned. Secondly, what is the purpose of undef ASM_SOFTMMU Thanks, Atif On 4/25/07, Atif Hashmi wrote: > > Hi Eduardo, > > Thanks for pointing me to the file. Could you please clarify one more > thing. > > Instructions like addl %ebx, (%eax) are also considered to be assembly > instructions. Do these type of instructions also refer to the functions that > you mentioned. > > Thanks, > Atif > > On 4/24/07, Eduardo Felipe wrote: > > > > Hi, > > > > You have a description of memory access instruction format in cpu-all.h, > > under > > /* CPU memory access without any memory or io remapping */ > > > > These instructions are defined in softmmu_header.h. If you don't care > > too much about performance it will be easier to modify the code written in C > > (undef ASM_SOFTMMU in op.c). > > > > Regards, > > Eduardo > > > ------=_Part_29268_7129340.1177519833537 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi Eduardo,

Thanks for pointing me to the file. Could you please clarify one more thing.

Instructions like addl %ebx, (%eax) are also considered to be memory refernce instructions. Do these type of instructions also refer to the functions that you mentioned.

Secondly, what is the purpose of undef ASM_SOFTMMU

Thanks,
Atif

On 4/25/07, Atif Hashmi < atifhashmi@gmail.com> wrote:
Hi Eduardo,

Thanks for pointing me to the file. Could you please clarify one more thing.

Instructions like addl %ebx, (%eax) are also considered to be assembly instructions. Do these type of instructions also refer to the functions that you mentioned.

Thanks,
Atif


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

You have a description of memory access instruction format in cpu-all.h, under
/* CPU memory access without any memory or io remapping */

These instructions are defined in softmmu_header.h. If you don't care too much about performance it will be easier to modify the code written in C (undef ASM_SOFTMMU in op.c).

Regards,
Eduardo


------=_Part_29268_7129340.1177519833537--