From: Petr Vorel <pvorel@suse.cz>
To: Martin Doucha <mdoucha@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v2 1/2] cve-2015-3290: Disable AVX for x86_64
Date: Mon, 7 Apr 2025 11:18:09 +0200 [thread overview]
Message-ID: <20250407091809.GA74858@pevik> (raw)
In-Reply-To: <a24e920b-4254-4cae-895d-64fdc0f5452e@suse.cz>
> Hi,
> one nit below.
> On 04. 04. 25 20:14, Siddhesh Poyarekar wrote:
> > When the input compiler enables AVX, stack realignment requirements
> > causes gcc to fail to omit %rbp use, due to which the test fails to
> > clobber %rbp in inline asm. Disable AVX to build the test on x86_64 so
> > that the test continues working.
> > Signed-off-by: Siddhesh Poyarekar <siddhesh@gotplt.org>
> > Reviewed-by: Martin Doucha <mdoucha@suse.cz>
> > ---
> > testcases/cve/Makefile | 6 ++++++
> > 1 file changed, 6 insertions(+)
> > diff --git a/testcases/cve/Makefile b/testcases/cve/Makefile
> > index 01b9b9ccb..d545a7f93 100644
> > --- a/testcases/cve/Makefile
> > +++ b/testcases/cve/Makefile
> > @@ -22,6 +22,12 @@ ifneq (,$(filter $(HOST_CPU),x86 x86_64))
> > meltdown: CFLAGS += -msse2
> > endif
> > +# The test needs to clobber %rbp, which requires frame pointer omission. Also
> > +# for x86_64, disable AVX since that could sometimes require a stack
> > +# realignment, which gets in the way of frame pointer omission.
> > cve-2015-3290: CFLAGS += -pthread -fomit-frame-pointer
> > +ifneq (,$(filter $(HOST_CPU),x86_64))
> If you don't want to add the command line option for 32bit x86 builds, then
> this condition would be cleaner:
> ifeq ($(HOST_CPU),x86_64)
+1. IMHO this works as expected. I suppose Siddhesh got inspiration for filter
due the above meltdown, where it is needed because it compares 2 archs. But
I will also appreciate an explicit confirmation.
Kind regards,
Petr
> We can fix that during merge but please confirm that we should.
> > +cve-2015-3290: CFLAGS += -mno-avx
> > +endif
> > include $(top_srcdir)/include/mk/generic_leaf_target.mk
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2025-04-07 9:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-02 17:07 [LTP] [PATCH] cve-2015-3290: Bump up stack boundary requirement Siddhesh Poyarekar
2025-04-03 15:07 ` Martin Doucha
2025-04-04 14:00 ` Petr Vorel
2025-04-04 14:20 ` Martin Doucha
2025-04-04 14:23 ` Siddhesh Poyarekar
2025-04-04 18:14 ` [LTP] [PATCH v2 0/2] cve-2015-3290: Disable AVX Siddhesh Poyarekar
2025-04-04 18:14 ` [LTP] [PATCH v2 1/2] cve-2015-3290: Disable AVX for x86_64 Siddhesh Poyarekar
2025-04-07 8:29 ` Martin Doucha
2025-04-07 9:18 ` Petr Vorel [this message]
2025-04-07 10:09 ` Siddhesh Poyarekar
2025-04-04 18:14 ` [LTP] [PATCH v2 2/2] Add centos10 to test matrix Siddhesh Poyarekar
2025-04-07 10:24 ` [LTP] [PATCH v3 0/2] cve-2015-3290: Disable AVX Siddhesh Poyarekar
2025-04-07 10:24 ` [LTP] [PATCH v3 1/2] cve-2015-3290: Disable AVX for x86_64 Siddhesh Poyarekar
2025-04-07 11:18 ` Petr Vorel
2025-04-07 10:24 ` [LTP] [PATCH v3 2/2] Add centos10 to test matrix Siddhesh Poyarekar
2025-04-07 11:13 ` Petr Vorel
2025-04-07 13:43 ` Siddhesh Poyarekar
2025-04-10 3:03 ` Li Wang via ltp
2025-04-10 14:50 ` Siddhesh Poyarekar
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=20250407091809.GA74858@pevik \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
--cc=mdoucha@suse.cz \
/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.