tes to memory. Can you tell me if it is sufficient enough to instrument
just those in ops_mem.h? I want to make sure I am not missing any form of
write to the memory (even it is from IO devices, which I think is taken care
of).
Thanks,
-Shashi.
On 5/17/07, Atif Hashmi <[EMAIL PROTECTED]> w
Hi,
Answering "1. Am I instrumenting all stores if I instrument the OPROTOs in
ops_mem.h? "
Do you consider all updates to memory as stores? e.g. add %ebx, (%eax), will
also write to the memory and
void OPPROTO glue(glue(op_stl, MEMSUFFIX), _T0_A0)(void) or one of its
variant will be called.
If
Hi Eduardo,
Is it possible to identify context switches inside QEMU. In order to support
transactional memory in QEMU, we have added
target_ulong tm_abort_eip;
int inTransaction;
to CPUX86State structure.
tm_abort_eip is the EIP to jump to when a transaction fails i.e. start of
the Transaction
do Felipe <[EMAIL PROTECTED]> wrote:
2007/4/25, Atif Hashmi <[EMAIL PROTECTED]>:
>
> 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.
No. You are
undef ASM_SOFTMMU
Thanks,
Atif
On 4/25/07, Atif Hashmi <[EMAIL PROTECTED]> 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
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 <[
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 s
t been able to figure it out why after calling helper_StartTransaction()
for the seconds time the program does not continue? Is their anything else
that we have not considered.
I will really appreciate your help.
Regards,
Atif
On 4/17/07, Eduardo Felipe <[EMAIL PROTECTED]> wrote:
Hi
20
But this prints "Transaction restart" once and then the program finishes.
This means that commit transaction is not called the second time. Could you
please tell me what am I doing wrong?
Regards,
Atif
On 4/16/07, Atif Hashmi <[EMAIL PROTECTED]> wrote:
On 4/8/0
Hi,
I have another small question. Actually, I am implementing hardware
transactional memory support in QEMU. I have implemented the following two
helper functions functions in targer-i386/helper.c
void helper_StartTransaction()
void helper_CommitTransaction();
My application looks as follows.
Hi Eduardo,
Thanks a lot for your help. I really appreciate it. I have added the
functionality that I wanted.
By the way, Is there any documentation that can help me better understand
the QEMU source code?
Regards,
Atif
On 4/8/07, Eduardo Felipe <[EMAIL PROTECTED]> wrote:
Hi Atif,
In target
Hi Eduardo,
I really appreciate your help but there is a small think that I need to ask
you.
In target-i386/translate.c, there are many variants of mov i.e.
case 0x89: /* mov Gv, Ev */
case 0xc7: /* mov Ev, Iv */
case 0x8b: /* mov Ev, Gv */
case 0x8e: /* mov seg, Gv */
which one do you think wi
Hi All,
Adding another note to my previous email. Is this even possible to do what I
am mentioned in my last email? (See Below)
Regards,
Atif
On 4/3/07, Atif Hashmi <[EMAIL PROTECTED]> wrote:
Hi All,
I am inserting
movl %eax, %eax
instruction within the assembly code of a program an
Hi All,
I am inserting
movl %eax, %eax
instruction within the assembly code of a program and I am running the code
on QEMU which is configured for i386 and is running linux-0.2.img.
I want to detect this assembly instruction within the QEMU code in order to
perform a specific operation e.g. wh
14 matches
Mail list logo
