From: Alan Kao <alankao@andestech.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Anup Patel <anup@brainfault.org>, Zong Li <zong@andestech.com>,
Albert Ou <aou@eecs.berkeley.edu>, Arnd Bergmann <arnd@arndb.de>,
<greentime@andestech.com>, Palmer Dabbelt <palmer@sifive.com>,
"linux-kernel@vger.kernel.org List"
<linux-kernel@vger.kernel.org>, <vincentc@andestech.com>,
<linux-riscv@lists.infradead.org>, <deanbo422@gmail.com>
Subject: Re: [RFC 0/2] RISC-V: A proposal to add vendor-specific code
Date: Thu, 1 Nov 2018 08:55:42 +0800 [thread overview]
Message-ID: <20181101005541.GA25604@andestech.com> (raw)
In-Reply-To: <20181031141745.GA5183@infradead.org>
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@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2018-11-01 0:55 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-31 10:35 [RFC 0/2] RISC-V: A proposal to add vendor-specific code Vincent Chen
2018-10-31 10:35 ` [RFC 1/2] RISC-V: An infrastructure " Vincent Chen
2018-10-31 10:35 ` [RFC 2/2] RISC-V: make dma_map_ops work without cache coherent agent Vincent Chen
2018-10-31 11:16 ` [RFC 0/2] RISC-V: A proposal to add vendor-specific code Anup Patel
2018-10-31 11:45 ` Arnd Bergmann
2018-10-31 14:17 ` Christoph Hellwig
2018-11-01 0:55 ` Alan Kao [this message]
2018-11-01 17:50 ` Palmer Dabbelt
2018-11-02 0:41 ` Alan Kao
2018-10-31 17:27 ` Palmer Dabbelt
2018-10-31 19:17 ` Olof Johansson
2018-11-01 17:48 ` Karsten Merker
2018-11-05 6:58 ` Vincent Chen
2018-11-05 7:05 ` Christoph Hellwig
2018-11-05 8:52 ` Arnd Bergmann
2018-11-05 9:08 ` Christoph Hellwig
2018-11-05 13:51 ` Arnd Bergmann
2018-11-06 6:59 ` Christoph Hellwig
2018-11-06 23:45 ` Palmer Dabbelt
2018-11-07 9:51 ` Arnd Bergmann
2018-11-06 23:45 ` Palmer Dabbelt
2018-11-08 2:43 ` Vincent Chen
2018-11-05 19:39 ` Nick Kossifidis
2018-11-06 6:56 ` Christoph Hellwig
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=20181101005541.GA25604@andestech.com \
--to=alankao@andestech.com \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=arnd@arndb.de \
--cc=deanbo422@gmail.com \
--cc=greentime@andestech.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@sifive.com \
--cc=vincentc@andestech.com \
--cc=zong@andestech.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;
as well as URLs for NNTP newsgroup(s).