From: "Rémi Denis-Courmont" <remi@remlab.net>
To: palmer@dabbelt.com, linux-riscv@lists.infradead.org
Cc: andy.chiu@sifive.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH -next v20 20/26] riscv: Add prctl controls for userspace vector management
Date: Wed, 24 May 2023 19:16:03 +0300 [thread overview]
Message-ID: <3656227.v5FYL8H6MN@basile.remlab.net> (raw)
In-Reply-To: <20230524092530.7773-1-andy.chiu@sifive.com>
Le keskiviikkona 24. toukokuuta 2023, 12.25.30 EEST Andy Chiu a écrit :
> How about adding the following 2 patches to deal with the problem.
> However, I am concerned if this makes ELF_HWCAP too complicated. e.g.
> Future extensions may as well want to do something here after we create
> an entry here.
Fine with me but I feel that we are missing the bigger picture here, as to
what the usage pattern/guideline for the prctl() on userspace side should be?
Maybe it was already discussed, and I just missed it, but I couldn't find it in
the documentation.
--
Rémi Denis-Courmont
http://www.remlab.net/
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2023-05-24 16:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2760633E-0DFA-4A72-AF4A-21613BEBA55D@remlab.net>
2023-05-24 0:18 ` [PATCH -next v20 20/26] riscv: Add prctl controls for userspace vector management Palmer Dabbelt
2023-05-24 9:25 ` Andy Chiu
2023-05-24 16:16 ` Rémi Denis-Courmont [this message]
2023-05-30 14:14 ` Andy Chiu
2023-05-24 16:13 ` Rémi Denis-Courmont
2023-05-18 16:19 [PATCH -next v20 00/26] riscv: Add vector ISA support Andy Chiu
2023-05-18 16:19 ` [PATCH -next v20 20/26] riscv: Add prctl controls for userspace vector management Andy Chiu
2023-05-20 14:11 ` kernel test robot
2023-05-21 1:50 ` kernel test robot
2023-05-21 5:38 ` Rémi Denis-Courmont
2023-05-22 8:28 ` Andy Chiu
2023-05-23 13:56 ` Björn Töpel
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=3656227.v5FYL8H6MN@basile.remlab.net \
--to=remi@remlab.net \
--cc=andy.chiu@sifive.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.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