| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20181101005541.GA25604@andestech.com>
Date: Thu, 1 Nov 2018 08:55:42 +0800
From: Alan Kao <alankao@...estech.com>
To: Christoph Hellwig <hch@...radead.org>
CC: Anup Patel <anup@...infault.org>, Zong Li <zong@...estech.com>,
Albert Ou <aou@...s.berkeley.edu>,
Arnd Bergmann <arnd@...db.de>, <greentime@...estech.com>,
Palmer Dabbelt <palmer@...ive.com>,
"linux-kernel@...r.kernel.org List" <linux-kernel@...r.kernel.org>,
<vincentc@...estech.com>, <linux-riscv@...ts.infradead.org>,
<deanbo422@...il.com>
Subject: Re: [RFC 0/2] RISC-V: A proposal to add vendor-specific code
On Wed, Oct 31, 2018 at 07:17:45AM -0700, Christoph Hellwig wrote:
> On Wed, Oct 31, 2018 at 04:46:10PM +0530, Anup Patel wrote:
> > I agree that we need a place for vendor-specific ISA extensions and
> > having vendor-specific directories is also good.
>
> The only sensible answer is that we should not allow vendor specific
> extensions in the kernel at all. ...
How can this even be possible if a extension includes an extra register
set as some domain-specific context? In such a case, kernel should
at least process the context during any context switch, just like how it
deals with the FP context.
> ... We need to standardize cache flushing
> and we need to do it soon and not introduce horrible bandaids because
> the foundation did not do its work.
>
> _______________________________________________
> linux-riscv mailing list
> linux-riscv@...ts.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-riscv
Powered by blists - more mailing lists