linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Luis Machado <luis.machado@arm.com>
Cc: linux-arm-kernel@lists.infradead.org
Subject: Re: RFC: FPA support removal from gdb and its impact on kgdb
Date: Thu, 6 Oct 2022 16:49:07 +0100	[thread overview]
Message-ID: <Yz7486VPQONArxla@shell.armlinux.org.uk> (raw)
In-Reply-To: <0bb128e7-14a3-4dc7-62b1-f3424155ee09@arm.com>

On Thu, Oct 06, 2022 at 02:42:09PM +0100, Luis Machado wrote:
> Hi Russel,
> 
> On 10/5/22 17:54, Russell King (Oracle) wrote:
> > Given this, and this is a fundamental interface between two different
> > pieces of software, I fail to see how you can even consider removing
> > support for this - if you remove support from gdb, then later gdb
> > will be unable to debug existing kernels.
> 
> It is being considered because not even the Linux kernel uses these
> registers anymore. The kgdb implementation was based on what GDB exposed
> long ago.

The kernel has never used the FPA not even an emulation of the FPA. The
kernel has provided a number of FPA emulation options over the years for
userspace to use, but never for its own use.

So kgdb's inclusion if these is merely to make kgdb's stub work with
gdb and nothing else.

> > In kernel-land, we have a rule: don't break userspace. I think there
> > should also be a rule for userspace: don't break the kernel!
> 
> That's fair, and I'm not seeking to proactively break the kernel. That's
> why I listed some possible solutions.
> 
> The best one is to update kgdb to send back XML data and drop the fp
> registers. On GDB's side, we can carry compatibility code that will
> guarantee things will work until it makes sense to remove the
> compatibility layer altogether.
> 
> Does that sound like a good compromise?

Yes, thanks.

-- 
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      reply	other threads:[~2022-10-06 15:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-05 15:03 RFC: FPA support removal from gdb and its impact on kgdb Luis Machado
2022-10-05 16:54 ` Russell King (Oracle)
2022-10-06 13:42   ` Luis Machado
2022-10-06 15:49     ` Russell King (Oracle) [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=Yz7486VPQONArxla@shell.armlinux.org.uk \
    --to=linux@armlinux.org.uk \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=luis.machado@arm.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 NNTP newsgroup(s).