All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Walmsley <pjw@kernel.org>
To: "Miquel Sabaté Solà" <mikisabate@gmail.com>
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
	 pjw@kernel.org, palmer@dabbelt.com, alex@ghiti.fr,
	wangyuli@uniontech.com
Subject: Re: [PATCH] riscv: kgdb: Ensure that BUFMAX > NUMREGBYTES
Date: Wed, 8 Oct 2025 11:28:02 -0600 (MDT)	[thread overview]
Message-ID: <2f6dd420-2bfd-794d-182c-74934577272d@kernel.org> (raw)
In-Reply-To: <68da3e6d.050a0220.c13dc.0f9a@mx.google.com>

[-- Attachment #1: Type: text/plain, Size: 936 bytes --]

On Mon, 29 Sep 2025, Miquel Sabaté Solà wrote:

> Miquel Sabaté Solà @ 2025-09-15 16:32 +02:
> 
> > The current value of BUFMAX is similar as in other architectures, but as
> > per documentation on KGDB (see
> > 'Documentation/process/debugging/kgdb.rst'), BUFMAX has to be larger
> > than NUMREGBYTES.
> >
> > Some NUMREGBYTES architectures (e.g. powerpc or hexagon) actually define
> > BUFMAX in relation to NUMREGBYTES, and thus this condition is always
> > guaranteed. Since 2048 is a value that is generally accepted on all
> > architectures, and that is larger than the current value of NUMREGBYTES,
> > we can keep this value in arch/riscv, but we can at least add an
> > 'static_assert' as an extra measure just in case NUMREGBYTES changes in
> > the future for some unforseen reason.
> >
> > Signed-off-by: Miquel Sabaté Solà <mikisabate@gmail.com>

[ ... ]

> Gentle ping :)

Thanks, queued for early v6.18-rc.


- Paul 

[-- Attachment #2: Type: text/plain, Size: 161 bytes --]

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

WARNING: multiple messages have this Message-ID (diff)
From: Paul Walmsley <pjw@kernel.org>
To: "Miquel Sabaté Solà" <mikisabate@gmail.com>
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
	 pjw@kernel.org, palmer@dabbelt.com, alex@ghiti.fr,
	wangyuli@uniontech.com
Subject: Re: [PATCH] riscv: kgdb: Ensure that BUFMAX > NUMREGBYTES
Date: Wed, 8 Oct 2025 11:28:02 -0600 (MDT)	[thread overview]
Message-ID: <2f6dd420-2bfd-794d-182c-74934577272d@kernel.org> (raw)
In-Reply-To: <68da3e6d.050a0220.c13dc.0f9a@mx.google.com>

[-- Attachment #1: Type: text/plain, Size: 936 bytes --]

On Mon, 29 Sep 2025, Miquel Sabaté Solà wrote:

> Miquel Sabaté Solà @ 2025-09-15 16:32 +02:
> 
> > The current value of BUFMAX is similar as in other architectures, but as
> > per documentation on KGDB (see
> > 'Documentation/process/debugging/kgdb.rst'), BUFMAX has to be larger
> > than NUMREGBYTES.
> >
> > Some NUMREGBYTES architectures (e.g. powerpc or hexagon) actually define
> > BUFMAX in relation to NUMREGBYTES, and thus this condition is always
> > guaranteed. Since 2048 is a value that is generally accepted on all
> > architectures, and that is larger than the current value of NUMREGBYTES,
> > we can keep this value in arch/riscv, but we can at least add an
> > 'static_assert' as an extra measure just in case NUMREGBYTES changes in
> > the future for some unforseen reason.
> >
> > Signed-off-by: Miquel Sabaté Solà <mikisabate@gmail.com>

[ ... ]

> Gentle ping :)

Thanks, queued for early v6.18-rc.


- Paul 

  reply	other threads:[~2025-10-08 17:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-15 14:32 [PATCH] riscv: kgdb: Ensure that BUFMAX > NUMREGBYTES Miquel Sabaté Solà
2025-09-15 14:32 ` Miquel Sabaté Solà
2025-09-29  8:08 ` Miquel Sabaté Solà
2025-09-29  8:08   ` Miquel Sabaté Solà
2025-10-08 17:28   ` Paul Walmsley [this message]
2025-10-08 17:28     ` Paul Walmsley

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=2f6dd420-2bfd-794d-182c-74934577272d@kernel.org \
    --to=pjw@kernel.org \
    --cc=alex@ghiti.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=mikisabate@gmail.com \
    --cc=palmer@dabbelt.com \
    --cc=wangyuli@uniontech.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.