That opcode is wrong. The opcode should be 0x0f 0x04, and then the
immediate value should be a 16 bit word which selects pseduo instruction
0x0043. The arguments to the pseudo instruction will be passed in the
according to the 64 bit x86 ABI, rdi and rsi.
You can ignore all these details if you compile m5.c and m5op_x86.S from
util/m5/ into your program, include m5op.h, and call the wrapper
function from C code.
Gabe
On 05/01/11 01:52, Muhammad Shoaib wrote:
> Hey,
>
> The op-code for the m5_checkpoint is 0x43.
> (./src/arch/x86/isa/decoder/two_byte_opcodes.isa:180: )
>
> Is it wrong to use this opcode directly for writing a checkpoint??
>
> test.c
> =======================
> int main()
> {
>
> __asm__ __volatile__(".byte 0x43\n");
>
> }
> =======================
>
> This is my rcS script for X86_FS ..
> ===================
> #!/bin/sh
> /sbin/swapon /dev/hdb
>
> cd /test
> /sbin/m5 dumpresetstats
> echo "Starting test"
> ./test.out ==> the executable
> echo "Done :D"
> /sbin/m5 exit
> /sbin/m5 exit
> ===================
>
> I am getting a seg fault after the system boots up, any idea ??
>
> Thanks
>
> Shoaib
> _______________________________________________
> m5-users mailing list
> [email protected]
> http://m5sim.org/cgi-bin/mailman/listinfo/m5-users
_______________________________________________
m5-users mailing list
[email protected]
http://m5sim.org/cgi-bin/mailman/listinfo/m5-users
