From: Ajit Kumar Agarwal <ajit.kumar.agarwal@xilinx.com>
To: Pedro Alves <palves@redhat.com>, Joel Brobecker <brobecker@adacore.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
Vinod Kathail <vinodk@xilinx.com>,
Vidhumouli Hunsigida <vidhum@xilinx.com>,
"Nagaraju Mekala" <nmekala@xilinx.com>
Subject: RE: [Patch] Microblaze: Port of Linux gdbserver
Date: Wed, 08 Oct 2014 14:59:00 -0000 [thread overview]
Message-ID: <837dac87732943cea0247f2a6e06097d@BY2FFO11FD060.protection.gbl> (raw)
With the below gdbserver Patch, here are the test results of running the gdb regression testsuite (gdb.base) . This tests results with the following patches already sent to FSF community for review.
GDB Client:
1. Add Little Endian breakpoint.
2. Add Software Single Step.
With the above GDB Client, below gdbserver patches are used.
=== gdb Summary ===
# of expected passes 7680
# of unexpected failures 2138
# of unexpected successes 2
# of expected failures 5
# of known failures 22
# of unresolved testcases 28
# of untested testcases 42
# of unsupported tests 124
Thanks & Regards
Ajit
-----Original Message-----
From: Ajit Kumar Agarwal
Sent: Wednesday, October 08, 2014 7:22 PM
To: 'Pedro Alves'; Michael Eager; Joel Brobecker
Cc: gdb-patches@sourceware.org; Vinod Kathail; Vidhumouli Hunsigida; Nagaraju Mekala
Subject: [Patch] Microblaze: Port of Linux gdbserver
Hello Pedro:
Please find the updated patch with feedback comments incorporated.
Microblaze: Port of Linux gdbserver
This patch is the port of Linux gdbserver.
Tested with gdb regression testsuite with this patch of
gdbserver.
gdb/:
2014-10-08 Ajit Agarwal <ajitkum@xilinx.com>
* configure.tgt (build_gdbserver): New Definition.
gdb/gdbserver/:
* gdbserver/Makefile.in (microblaze-linux.c): New target.
* gdbserver/configure.srv (microblaze*-*-linux*): New target.
* gdbserver/linux-microblaze-low.c: New file.
Signed-off-by:Ajit Agarwal ajitkum@xilinx.com
Thanks & Regards
Ajit
-----Original Message-----
From: Pedro Alves [mailto:palves@redhat.com]
Sent: Tuesday, September 30, 2014 5:14 PM
To: Ajit Kumar Agarwal; Michael Eager; Joel Brobecker
Cc: gdb-patches@sourceware.org; Vinod Kathail; Vidhumouli Hunsigida; Nagaraju Mekala
Subject: Re: [Patch, microblaze]: Port of Linux gdbserver
On 09/23/2014 01:49 PM, Ajit Kumar Agarwal wrote:
>>>> >>> Note nothing is done with valid_p. It's write-only. Compare with other ports, like arm-tdep.c or mips-tdep.c.
>> >
>> > Would look into this and will make the modification.
> Thanks.
I'd much prefer if we had that patch in the tree before accepting further patches that tweak things around register names, etc. Could you send that (as an independent patch, in a new thread).
> +#define microblaze_num_regs \
> + (sizeof microblaze_regmap / sizeof microblaze_regmap[0])
#define microblaze_num_regs ARRAY_SIZE (microblaze_regmap)
> +
> +static int
> +microblaze_cannot_store_register (int regno) {
> + if (microblaze_regmap[regno] == -1 || regno == 0)
> + return 1;
> +
> + return 0;
> +}
> +
> +static int
> +microblaze_cannot_fetch_register (int regno) {
> + return 0;
> +}
> +
> +static CORE_ADDR
> +microblaze_get_pc (struct regcache *regcache) {
> + unsigned long pc;
> + collect_register_by_name (regcache, "rpc", &pc);
Empty line after declaration. In several more places in the patch.
Please fix them all.
> + return (CORE_ADDR) (pc);
> +}
> + if (regno == 0)
> + {
> + unsigned long regbuf_0 = 0;
> + /* Clobbering r0 so that it is always 0 as enforced by hardware. */
> + supply_register (regcache, regno, (const char*)®buf_0);
supply_register_zeroed (regcache, regno);
> + }
> + else
> + {
> + if (size < sizeof (long))
> + supply_register (regcache, regno, buf + sizeof (long) - size);
> + else
> + supply_register (regcache, regno, buf);
> + }
> +}
> +
> +/* Provide only a fill function for the general register set. ps_lgetregs
> + will use this for NPTL support. */
> +
> +static void microblaze_fill_gregset (struct regcache *regcache, void
> +*buf)
Line break after "static void". Function name goes on column 0:
static void
microblaze_fill_gregset (struct regcache *regcache, void *buf)
Please make sure that's correct throughout.
> +{
> + int i;
> +
> + for (i = 0; i < microblaze_num_regs; i++)
> + microblaze_collect_ptrace_register (regcache, i,
> + (char *) buf +
> +microblaze_regmap[i]); }
> +
> +static void
> +microblaze_store_gregset (struct regcache *regcache, const void *buf)
> +{
> + int i;
> + for (i = 0; i < microblaze_num_regs; i++)
> + supply_register (regcache, i, (char *) buf +
> +microblaze_regmap[i]); }
> +
> +#endif /* HAVE_PTRACE_GETREGS */
> +
> +static struct regset_info microblaze_regsets[] = { #ifdef
> +HAVE_PTRACE_GETREGS
What's the #ifdef for?
Did this kernel port make it upstream without PTRACE_GETREGSET?
If there's support for that, can you please switch to using it?
PTRACE_GETREGS is supposed to an old way of doing things...
> + { PTRACE_GETREGS, PTRACE_SETREGS, 0, 36 * sizeof (elf_gregset_t),
> + GENERAL_REGS, microblaze_fill_gregset, microblaze_store_gregset
> +},
> + { 0, 0, 0, -1, -1, NULL, NULL },
> +#endif /* HAVE_PTRACE_GETREGS */
> + { 0, 0, 0, -1, -1, NULL, NULL }
> +};
> +
> diff --git a/gdb/regformats/microblaze-with-stack-protect.dat
> b/gdb/regformats/microblaze-with-stack-protect.dat
> index f71c111..e349b4a 100644
> --- a/gdb/regformats/microblaze-with-stack-protect.dat
> +++ b/gdb/regformats/microblaze-with-stack-protect.dat
> @@ -1,7 +1,7 @@
> # DO NOT EDIT: generated from microblaze-with-stack-protect.xml
^^^^^^^^^^^
^^^^^^^^^^^
^^^^^^^^^^^
^^^^^^^^^^^
^^^^^^^^^^^
Please send a preparatory, independent, patch that updates features/Makefile instead and generates this file, in a new thread, with self-contained description, following the
checklist:
https://sourceware.org/gdb/wiki/ContributionChecklist
> name:microblaze_with_stack_protect
> xmltarget:microblaze-with-stack-protect.xml
> -expedite:r1,pc
> +expedite:r1,rpc
> 32:r0
> 32:r1
> 32:r2
> -- 1.7.1
>
Thanks,
Pedro Alves
next reply other threads:[~2014-10-08 14:59 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-08 14:59 Ajit Kumar Agarwal [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-10-08 13:52 Ajit Kumar Agarwal
2014-10-09 16:29 ` Michael Eager
2014-10-09 18:54 ` Ajit Kumar Agarwal
2014-10-09 23:42 ` Michael Eager
2014-10-13 16:00 ` Ajit Kumar Agarwal
2014-10-13 17:49 ` Michael Eager
2014-10-14 3:03 ` Ajit Kumar Agarwal
2014-10-14 15:07 ` Michael Eager
2014-10-14 15:33 ` Ajit Kumar Agarwal
2014-10-14 15:42 ` Ajit Kumar Agarwal
2014-10-15 13:27 ` Pedro Alves
2014-10-17 19:22 ` Ajit Kumar Agarwal
2014-12-15 18:02 ` Pedro Alves
2014-12-15 18:13 ` Michael Eager
2014-12-18 8:58 ` Ajit Kumar Agarwal
2014-12-18 16:10 ` Michael Eager
2014-12-18 8:57 ` Ajit Kumar Agarwal
2014-12-18 11:28 ` Pedro Alves
2014-12-18 16:53 ` Ajit Kumar Agarwal
2014-12-18 17:40 ` Pedro Alves
2014-12-19 8:27 ` Ajit Kumar Agarwal
2014-12-19 10:56 ` Pedro Alves
2014-12-19 10:26 ` Ajit Kumar Agarwal
2014-12-19 11:02 ` Pedro Alves
2014-12-19 18:06 ` Ajit Kumar Agarwal
2014-11-26 12:13 ` Ajit Kumar Agarwal
2014-12-15 16:08 ` Ajit Kumar Agarwal
2014-09-10 10:14 [Patch, microblaze]: " Ajit Kumar Agarwal
2014-09-10 13:31 ` Michael Eager
2014-09-10 13:46 ` Joel Brobecker
2014-09-10 14:23 ` Ajit Kumar Agarwal
2014-09-10 14:39 ` Michael Eager
2014-09-10 14:59 ` Ajit Kumar Agarwal
2014-09-10 15:12 ` Ajit Kumar Agarwal
2014-09-10 15:27 ` Michael Eager
2014-09-10 15:30 ` Ajit Kumar Agarwal
2014-09-10 15:35 ` Michael Eager
2014-09-10 15:51 ` Ajit Kumar Agarwal
2014-09-10 14:43 ` Joel Brobecker
2014-09-10 15:04 ` Ajit Kumar Agarwal
2014-09-10 15:54 ` Joel Brobecker
2014-09-10 16:10 ` Ajit Kumar Agarwal
2014-09-12 8:01 ` Ajit Kumar Agarwal
2014-09-12 8:39 ` Ajit Kumar Agarwal
2014-09-12 15:38 ` Michael Eager
2014-09-16 6:42 ` Ajit Kumar Agarwal
2014-09-16 12:06 ` Michael Eager
2014-09-17 9:36 ` Ajit Kumar Agarwal
2014-09-17 14:12 ` Michael Eager
2014-09-16 17:04 ` Pedro Alves
2014-09-17 6:16 ` Ajit Kumar Agarwal
2014-09-17 8:15 ` Pedro Alves
2014-09-17 8:20 ` Ajit Kumar Agarwal
2014-09-23 12:49 ` Ajit Kumar Agarwal
2014-09-30 11:43 ` Pedro Alves
2014-09-30 13:27 ` Ajit Kumar Agarwal
2014-09-30 13:37 ` Pedro Alves
2014-09-30 14:21 ` Ajit Kumar Agarwal
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=837dac87732943cea0247f2a6e06097d@BY2FFO11FD060.protection.gbl \
--to=ajit.kumar.agarwal@xilinx.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=nmekala@xilinx.com \
--cc=palves@redhat.com \
--cc=vidhum@xilinx.com \
--cc=vinodk@xilinx.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).