From: Simon Marchi <simark@simark.ca>
To: Tankut Baris Aktemur <tankutbaris.aktemur@amd.com>,
gdb-patches@sourceware.org, lancelot.six@amd.com
Subject: Re: [PATCH v2] gdb, amdgpu: add config guards for AMD_DBGAPI_STATUS_ERROR_MEMORY_UNAVAILABLE
Date: Thu, 15 Oct 2026 15:03:55 -0400 [thread overview]
Message-ID: <fc78be29-3a2a-4ec5-a358-d382b74cf636@simark.ca> (raw)
In-Reply-To: <20261015181527.4178032-1-tankutbaris.aktemur@amd.com>
On 10/15/26 2:15 PM, Tankut Baris Aktemur wrote:
> diff --git a/gdb/configure.ac b/gdb/configure.ac
> index e0117ede292..7a437747e35 100644
> --- a/gdb/configure.ac
> +++ b/gdb/configure.ac
> @@ -368,6 +368,27 @@ if test "$gdb_require_amd_dbgapi" = true \
> AC_MSG_ERROR([amd-dbgapi not supported for host ${gdb_host}])
> ;;
> esac
> +
> + # Detect if AMD_DBGAPI_STATUS_ERROR_MEMORY_UNAVAILABLE can be used.
As a person who likes to clean up obsolete code, may I ask you to
mention which dbgapi version introduced
AMD_DBGAPI_STATUS_ERROR_MEMORY_UNAVAILABLE? This way it will become easier
to spot when this configure check is no longer necessary.
Simon
next prev parent reply other threads:[~2026-10-15 19:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-15 18:15 Tankut Baris Aktemur
2026-10-15 19:03 ` Simon Marchi [this message]
2026-10-16 6:52 ` Aktemur, Baris
2026-10-19 15:00 ` Six, Lancelot
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=fc78be29-3a2a-4ec5-a358-d382b74cf636@simark.ca \
--to=simark@simark.ca \
--cc=gdb-patches@sourceware.org \
--cc=lancelot.six@amd.com \
--cc=tankutbaris.aktemur@amd.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