From: Omair Javaid <omair.javaid@linaro.org>
To: Yao Qi <yao@codesourcery.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH 4/7] Implements aarch64 process record and reverse debugging support
Date: Mon, 01 Sep 2014 20:08:00 -0000 [thread overview]
Message-ID: <CANW4E-0SPFqsHo4QCyoMjJHHPVVm_fNsNfdpTTapwfKu3=r4iA@mail.gmail.com> (raw)
In-Reply-To: <87k35q8xuf.fsf@codesourcery.com>
On 30 August 2014 08:23, Yao Qi <yao@codesourcery.com> wrote:
> Omair Javaid <omair.javaid@linaro.org> writes:
>
>> This patch defines structures, macros and functions required for process record
>> and reverse debugging support on aarch64-linux targets. Also implements
>> support for recording most if not all of instructions from a64 instruction set.
>>
>> gdb:
>>
>> 2014-06-04 Omair Javaid <omair.javaid@linaro.org>
>>
>> * aarch64-linux-tdep.c (aarch64_linux_init_abi): Updated.
>> * aarch64-tdep.c (record.h): Include.
>> (record-full.h): Include.
>> (aarch64_record_data_proc_reg): New function.
>> (aarch64_record_data_proc_imm): New function.
>> (aarch64_record_branch_except_sys): New function.
>> (aarch64_record_load_store): New function.
>> (aarch64_record_decode_insn_handler): New function.
>> (deallocate_reg_mem): New function.
>> (aarch64_process_record): New function.
>> * aarch64-tdep.h (submask): New macro.
>> (bit): New macro.
>> (bits): New macro.
>> (REG_ALLOC): New macro.
>> (MEM_ALLOC): New macro.
>> (struct aarch64_mem_r): Defined.
>> (aarch64_record_result): New enum.
>> (struct insn_decode_record): Defined.
>> (insn_decode_record): New typedef.
>> (aarch64_process_record): New extern declaration.
>
> We want to support process record on aarch64-linux, but the code is
> added to aarch64-tdep.c. Does aarch64-elf target need process record?
> I prefer to add code to aarch64-linux-tdep.c. I know that code for
> process record on arm was added to arm-tdep.c too, but I don't think it
> is correct either.
If we try Record-Replay can work on any target running a gdb stub with
a little tweaking but we do need a linux host machine in all cases.
so I think *-tdep.c is the right place for it. Thats the reason
syscall recording code resides in *-linux-tdep.c but all other
instruction recording code is in *-tdep.c
>
>> diff --git a/gdb/aarch64-tdep.h b/gdb/aarch64-tdep.h
>> index 78fb779..8a193f4 100644
>> --- a/gdb/aarch64-tdep.h
>> +++ b/gdb/aarch64-tdep.h
>> @@ -90,4 +90,69 @@ struct gdbarch_tdep
>> struct type *vnb_type;
>> };
>>
>> +/* aarch64 process record-replay related structures, defines etc. */
>> +
>> +#define submask(x) ((1L << ((x) + 1)) - 1)
>> +#define bit(obj,st) (((obj) >> (st)) & 1)
>> +#define bits(obj,st,fn) (((obj) >> (st)) & submask ((fn) - (st)))
>
> If they are only used in aarch64-tdep.c, please define them there.
OK
>
>> +
>> +/* ARM memory record structure. */
>
> s/ARM/AArch64/
OK
>
>> +struct aarch64_mem_r
>> +{
>> + uint64_t len; /* Record length. */
>> + uint64_t addr; /* Memory address. */
>> +};
>> +
>> +enum aarch64_record_result
>> +{
>> + AARCH64_RECORD_SUCCESS,
>> + AARCH64_RECORD_FAILURE,
>> + AARCH64_RECORD_USUPPORTED
>> +};
>> +
>> +/* ARM instruction record contains opcode of current insn
OK
>
> Likewise.
>
> --
> Yao (齐尧)
next prev parent reply other threads:[~2014-09-01 20:08 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-04 16:21 [PATCH 0/7] Process record and reverse debugging support on aarch64-linux Omair Javaid
2014-06-04 16:21 ` [PATCH 1/7] NEWS entry about aarch64-linux record/replay support Omair Javaid
2014-06-04 16:24 ` Eli Zaretskii
2014-08-30 2:40 ` Yao Qi
2014-09-01 14:51 ` Marcus Shawcroft
2014-09-02 1:01 ` Yao Qi
2014-09-17 23:30 ` [PATCH] " Omair Javaid
2014-09-18 2:53 ` Eli Zaretskii
2014-06-04 16:21 ` [PATCH 4/7] Implements aarch64 process record and reverse debugging support Omair Javaid
2014-06-05 8:34 ` Will Newton
2014-08-28 22:17 ` Omair Javaid
2014-08-30 3:27 ` Yao Qi
2014-09-01 20:08 ` Omair Javaid [this message]
2014-09-18 0:09 ` Omair Javaid
2014-09-18 22:29 ` Omair Javaid
2014-10-14 12:48 ` Omair Javaid
2014-10-21 9:08 ` Omair Javaid
2014-06-04 16:21 ` [PATCH 7/7] Enables gdb.reverse testsuite for aarch64*-linux targets Omair Javaid
2014-06-05 9:00 ` Will Newton
2014-10-21 9:10 ` Omair Javaid
2014-06-04 16:21 ` [PATCH 6/7] Support for recording aarch64 advance simd instructions Omair Javaid
2014-06-05 8:58 ` Will Newton
2014-08-29 13:41 ` [PATCH 6/7] Support for recording aarch64 advanced SIMD instructions Omair Javaid
2014-09-02 15:01 ` Will Newton
2014-06-04 16:21 ` [PATCH 5/7] Support for recording syscall on aarch64-linux Omair Javaid
2014-06-05 8:52 ` Will Newton
2014-06-06 15:58 ` Andreas Arnez
2014-06-11 7:11 ` Omair Javaid
2014-08-29 11:53 ` Omair Javaid
2014-09-18 0:23 ` Will Newton
2014-09-18 22:28 ` Omair Javaid
2014-10-14 12:47 ` Omair Javaid
2014-10-21 9:09 ` Omair Javaid
2014-06-04 16:21 ` [PATCH 3/7] Enable gdb process record on aarch64-linux targets Omair Javaid
2014-06-05 9:00 ` Will Newton
2014-08-30 3:35 ` Yao Qi
2014-09-01 19:50 ` Omair Javaid
2014-06-04 16:21 ` [PATCH 2/7] Fixes for aarch64-linux gdb core file support Omair Javaid
2014-06-04 17:11 ` Andreas Arnez
2014-06-05 17:09 ` Omair Javaid
2014-08-28 13:49 ` [PATCH 2/7] Fixes for aarch64-linux " Omair Javaid
2014-08-30 3:00 ` Yao Qi
2014-09-01 19:38 ` Omair Javaid
2014-09-17 23:37 ` Re " Omair Javaid
2014-10-14 12:49 ` Omair Javaid
2014-10-21 9:07 ` Omair Javaid
2014-10-21 13:28 ` Yao Qi
2014-10-27 12:33 ` Omair Javaid
2014-06-05 9:07 ` [PATCH 2/7] Fixes for aarch64-linux gdb " Will Newton
2014-06-23 10:41 ` [PATCH 0/7] Process record and reverse debugging support on aarch64-linux Omair Javaid
2014-08-30 3:45 ` Yao Qi
2014-09-01 19:42 ` Omair Javaid
2014-09-02 1:12 ` Yao Qi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CANW4E-0SPFqsHo4QCyoMjJHHPVVm_fNsNfdpTTapwfKu3=r4iA@mail.gmail.com' \
--to=omair.javaid@linaro.org \
--cc=gdb-patches@sourceware.org \
--cc=yao@codesourcery.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox