From: hch@infradead.org (Christoph Hellwig)
To: linux-riscv@lists.infradead.org
Subject: [PATCH v2] riscv: Add support to no-FPU systems
Date: Fri, 29 Jun 2018 00:26:36 -0700 [thread overview]
Message-ID: <20180629072636.GA4416@infradead.org> (raw)
In-Reply-To: <20180629072229.GE12956@infradead.org>
Btw, I wonder if we just just move __restore_d_state/__save_d_state
to assembly. They just call assembly routines to start with, so
they might be a natural fit for the new fpu.S file.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Alan Kao <alankao@andestech.com>
Cc: Zong Li <zong@andestech.com>, Andrew Waterman <andrew@sifive.com>,
Arnd Bergmann <arnd@arndb.de>,
Greentime <greentime@andestech.com>,
Darius Rad <darius@bluespec.com>,
Palmer Dabbelt <palmer@sifive.com>,
linux-kernel@vger.kernel.org,
Christoph Hellwig <hch@infradead.org>,
Albert Ou <albert@sifive.com>,
linux-riscv@lists.infradead.org
Subject: Re: [PATCH v2] riscv: Add support to no-FPU systems
Date: Fri, 29 Jun 2018 00:26:36 -0700 [thread overview]
Message-ID: <20180629072636.GA4416@infradead.org> (raw)
In-Reply-To: <20180629072229.GE12956@infradead.org>
Btw, I wonder if we just just move __restore_d_state/__save_d_state
to assembly. They just call assembly routines to start with, so
they might be a natural fit for the new fpu.S file.
next prev parent reply other threads:[~2018-06-29 7:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-27 4:22 [PATCH v2] riscv: Add support to no-FPU systems Alan Kao
2018-06-27 4:22 ` Alan Kao
2018-06-29 7:22 ` Christoph Hellwig
2018-06-29 7:22 ` Christoph Hellwig
2018-06-29 7:26 ` Christoph Hellwig [this message]
2018-06-29 7:26 ` Christoph Hellwig
2018-08-01 17:55 ` Palmer Dabbelt
2018-08-01 17:55 ` Palmer Dabbelt
2018-08-01 18:23 ` Andrew Waterman
2018-08-01 18:23 ` Andrew Waterman
2018-08-04 4:03 ` Palmer Dabbelt
2018-08-04 4:03 ` Palmer Dabbelt
2018-08-05 23:32 ` Alan Kao
2018-08-05 23:32 ` Alan Kao
2018-08-01 23:09 ` Alan Kao
2018-08-01 23:09 ` Alan Kao
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=20180629072636.GA4416@infradead.org \
--to=hch@infradead.org \
--cc=linux-riscv@lists.infradead.org \
/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.