public inbox for debugedit@sourceware.org
 help / color / mirror / Atom feed
From: "Ivan A. Melnikov" <iv@altlinux.org>
To: Mark Wielaard <mark@klomp.org>
Cc: "Dmitry V. Levin" <ldv@altlinux.org>, debugedit@sourceware.org
Subject: Re: [PATCH] debugedit: add MIPS support
Date: Fri, 9 Apr 2021 14:17:03 +0400	[thread overview]
Message-ID: <20210409101703.w7kcyqnaxwalbl5e@titan.localdomain> (raw)
In-Reply-To: <20210402230309.GW2685@wildebeest.org>

On Sat, Apr 03, 2021 at 01:03:09AM +0200, Mark Wielaard wrote:
> Hi Dmitry, Hi Ivan,

Hi Mark,

Sorry for slow reply.

> On Fri, Apr 02, 2021 at 08:00:00AM +0000, Dmitry V. Levin wrote:
> > From: "Ivan A. Melnikov" <iv@altlinux.org>
> > Date: Fri, 13 Nov 2020 15:51:08 +0400
> > 
> > According to the specification[1], all MIPS .debug_* sections are
> > marked with ELF type SHT_MIPS_DWARF.  The format of the section
> > data stays the same, so we have can handle e.g. .debug_info
> > section as we used to.
> > 
> > As SHT_MIPS_DWARF is from processor-specific range, we have to check
> > that we're actually dealing with MIPS ELF file before handling such
> > sections.
> > 
> > [1] MIPS Extensions to DWARF Version 2.0. -- Silicon Graphics
> >     Computer Systems, rev 1.17, 29 Aug 2001
> > 
> > Refs: https://bugzilla.altlinux.org/39284
> > Signed-off-by: Ivan A. Melnikov <iv@altlinux.org>
> > Signed-off-by: Dmitry V. Levin <ldv@altlinux.org>
> 
> This looks correct. I have pushed it to main. 

Thank you.

> I don't have a MIPS setup to check, but don't you
> also need some R_MIPS value for setup_relbuf?

The thing is that there are several MIPS ABIs. Our
primary target is MIPS32 with o32 (traditional) ABI.
With this ABI, RELA relocations are not used,
even for kernel modules, so all the relocations
in .debug_info sections are "uniteresting", as the
comment in setup_relbuf calls them.

So, my patch is enough to support MIPS32 systems
with o32 ABI.

On the other hand, on MIPS64 systems with n64 ABI
(the most whidespread ABI on 64-bit MIPS) at least
4 types of RELA relocations are used. They,
indeed, should be added to setup_relbuf, and some
of them may even require additional handling.
I'm looking into that, but I haven't figured out
all the details yet. I'll send a patch here when
I'll have something.

-- 
  wbr,
    iv m.

      reply	other threads:[~2021-04-09 10:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-02  8:00 Dmitry V. Levin
2021-04-02 23:03 ` Mark Wielaard
2021-04-09 10:17   ` Ivan A. Melnikov [this message]

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=20210409101703.w7kcyqnaxwalbl5e@titan.localdomain \
    --to=iv@altlinux.org \
    --cc=debugedit@sourceware.org \
    --cc=ldv@altlinux.org \
    --cc=mark@klomp.org \
    /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).