Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   =?ISO-8859-1?Q?R=E9mi?= 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
Message-ID: <3656227.v5FYL8H6MN@basile.remlab.net>
Organization: Remlab
In-Reply-To: <20230524092530.7773-1-andy.chiu@sifive.com>
References: <mhng-52f8af07-f3fc-4674-94ea-abbe2108907a@palmer-ri-x1c9a>
 <20230524092530.7773-1-andy.chiu@sifive.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 8BIT
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

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/