public inbox for dtrace@lists.linux.dev
 help / color / mirror / Atom feed
From: Kris Van Hees <kris.van.hees@oracle.com>
To: eugene.loh@oracle.com
Cc: dtrace@lists.linux.dev, dtrace-devel@oss.oracle.com
Subject: Re: [PATCH 5/5] test: Remove antiquated special case for aarch64
Date: Thu, 2 Oct 2025 23:55:51 -0400	[thread overview]
Message-ID: <aN9JRyb0vC7Cs8k8@oracle.com> (raw)
In-Reply-To: <20251001062418.6902-5-eugene.loh@oracle.com>

On Wed, Oct 01, 2025 at 02:24:18AM -0400, eugene.loh@oracle.com wrote:
> From: Eugene Loh <eugene.loh@oracle.com>
> 
> Also, add some compilation flags while we are at it.
> 
> Signed-off-by: Eugene Loh <eugene.loh@oracle.com>

Reviewed-by: Kris Van Hees <kris.van.hees@oracle.com>

> ---
>  test/triggers/Build                         | 1 +
>  test/unittest/ustack/tst.bigstack.aarch64.x | 2 --
>  2 files changed, 1 insertion(+), 2 deletions(-)
>  delete mode 100644 test/unittest/ustack/tst.bigstack.aarch64.x
> 
> diff --git a/test/triggers/Build b/test/triggers/Build
> index d49b996a6..4ff5002a8 100644
> --- a/test/triggers/Build
> +++ b/test/triggers/Build
> @@ -236,6 +236,7 @@ usdt-tst-special_PROV := usdt-tst-special-prov.d
>  # ustack wants no optimization
>  
>  ustack-tst-basic_CFLAGS := -O0 -fno-inline -fno-omit-frame-pointer
> +ustack-tst-bigstack_CFLAGS := -O0 -fno-inline -fno-omit-frame-pointer
>  ustack-tst-bigstack-spin_CFLAGS := -O0 -fno-inline -fno-omit-frame-pointer
>  ustack-tst-spin_CFLAGS := -O0
>  ustack-tst-mtspin_CFLAGS := -O0
> diff --git a/test/unittest/ustack/tst.bigstack.aarch64.x b/test/unittest/ustack/tst.bigstack.aarch64.x
> deleted file mode 100644
> index 735f88c35..000000000
> --- a/test/unittest/ustack/tst.bigstack.aarch64.x
> +++ /dev/null
> @@ -1,2 +0,0 @@
> -# On aarch64, we are able to handle ustackdepth beyond 4096 so the expected
> -# BAD_STACK failure will not occur with this test.
> -- 
> 2.47.3
> 

  reply	other threads:[~2025-10-03  3:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-01  6:24 [PATCH 1/5] test: Use a more ubiquitous probe for return()-action tests eugene.loh
2025-10-01  6:24 ` [PATCH 2/5] test: Adjust skip file for lockmem problem eugene.loh
2025-10-03  3:52   ` Kris Van Hees
2025-10-01  6:24 ` [PATCH 3/5] test: Fix some ustackdepth tests eugene.loh
2025-10-03  4:07   ` Kris Van Hees
2025-10-09 16:29     ` Kris Van Hees
2025-10-09 21:11       ` Eugene Loh
2025-10-01  6:24 ` [PATCH 4/5] test: Fix antiquated reference to dtrace_ustackdepth_max eugene.loh
2025-10-03  3:56   ` Kris Van Hees
2025-10-01  6:24 ` [PATCH 5/5] test: Remove antiquated special case for aarch64 eugene.loh
2025-10-03  3:55   ` Kris Van Hees [this message]
2025-10-03  3:50 ` [PATCH 1/5] test: Use a more ubiquitous probe for return()-action tests Kris Van Hees

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=aN9JRyb0vC7Cs8k8@oracle.com \
    --to=kris.van.hees@oracle.com \
    --cc=dtrace-devel@oss.oracle.com \
    --cc=dtrace@lists.linux.dev \
    --cc=eugene.loh@oracle.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