From: Richard Henderson <richard.henderson@linaro.org>
To: Michael Clark <mjc@sifive.com>
Cc: qemu-devel@nongnu.org,
Bastian Koppelmann <kbastian@mail.uni-paderborn.de>,
Palmer Dabbelt <palmer@sifive.com>,
Sagar Karandikar <sagark@eecs.berkeley.edu>,
RISC-V Patches <patches@groups.riscv.org>
Subject: Re: [Qemu-devel] [PATCH v3 06/21] RISC-V FPU Support
Date: Thu, 11 Jan 2018 12:01:41 -0800 [thread overview]
Message-ID: <c97716bd-69fa-c7d5-5e27-af8201e6d999@linaro.org> (raw)
In-Reply-To: <CAHNT7Ns5GKU0g9V2DwbQWO0ahjE67+OO0gYnEyU+88BjXghKJg@mail.gmail.com>
On 01/11/2018 10:09 AM, Michael Clark wrote:
>
> The RISC-V QEMU port is presently quite usable, and we have fedora and debian
> folk both working on packacking for RISC-V. The general sentiment is does our
> port need to be perfect to be accepted in-tree? or can we work on clean-ups and
> bug fixes in tree? We're pretty committed to transforming it into a high
> quality port and we will have plently of time going forward to address any
> issues. We have to balance cleanups and bug fixes for corner cases with adding
> and improve device emulation support. So far all of the recent effort has gone
> into the former, i.e. clean-ups and bug fixes, so you can be sure we will
> attend to any remaining issues in the comitted blocks of time we have available
> to work on the port.
No, it doesn't have to be perfect to go in. I would like the actual errors
fixed before going in; but I suppose this fp stuff falls into the "just
cleanup" category.
r~
next prev parent reply other threads:[~2018-01-11 20:01 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-11 2:21 [Qemu-devel] [PATCH v3 00/21] RISC-V QEMU Port Submission v3 Michael Clark
2018-01-11 2:21 ` [Qemu-devel] [PATCH v3 01/21] RISC-V Maintainers Michael Clark
2018-01-11 2:21 ` [Qemu-devel] [PATCH v3 02/21] RISC-V ELF Machine Definition Michael Clark
2018-01-11 2:21 ` [Qemu-devel] [PATCH v3 03/21] RISC-V CPU Core Definition Michael Clark
2018-01-11 14:32 ` Richard Henderson
2018-01-11 14:37 ` Richard Henderson
2018-01-11 17:55 ` Michael Clark
2018-01-12 3:03 ` Palmer Dabbelt
2018-01-11 2:21 ` [Qemu-devel] [PATCH v3 04/21] RISC-V Disassembler Michael Clark
2018-01-11 14:34 ` Richard Henderson
2018-01-11 2:21 ` [Qemu-devel] [PATCH v3 05/21] RISC-V CPU Helpers Michael Clark
2018-01-11 15:29 ` Richard Henderson
2018-01-11 2:21 ` [Qemu-devel] [PATCH v3 06/21] RISC-V FPU Support Michael Clark
2018-01-11 15:31 ` Richard Henderson
2018-01-11 18:09 ` Michael Clark
2018-01-11 20:01 ` Richard Henderson [this message]
2018-01-11 2:21 ` [Qemu-devel] [PATCH v3 07/21] RISC-V GDB Stub Michael Clark
2018-01-11 15:31 ` Richard Henderson
2018-01-11 2:21 ` [Qemu-devel] [PATCH v3 08/21] RISC-V TCG Code Generation Michael Clark
2018-01-11 15:47 ` Richard Henderson
2018-01-11 18:15 ` Michael Clark
2018-01-11 18:55 ` Michael Clark
2018-01-11 2:21 ` [Qemu-devel] [PATCH v3 09/21] RISC-V Physical Memory Protection Michael Clark
2018-01-11 2:21 ` [Qemu-devel] [PATCH v3 10/21] RISC-V Linux User Emulation Michael Clark
2018-01-11 2:21 ` [Qemu-devel] [PATCH v3 11/21] RISC-V HTIF Console Michael Clark
2018-01-11 2:21 ` [Qemu-devel] [PATCH v3 12/21] RISC-V HART Array Michael Clark
2018-01-11 2:21 ` [Qemu-devel] [PATCH v3 13/21] SiFive RISC-V CLINT Block Michael Clark
2018-01-11 2:21 ` [Qemu-devel] [PATCH v3 14/21] SiFive RISC-V PLIC Block Michael Clark
2018-01-11 9:10 ` Antony Pavlov
2018-01-11 2:21 ` [Qemu-devel] [PATCH v3 15/21] RISC-V Spike Machines Michael Clark
2018-01-11 2:21 ` [Qemu-devel] [PATCH v3 16/21] RISC-V VirtIO Machine Michael Clark
2018-01-11 2:22 ` [Qemu-devel] [PATCH v3 17/21] SiFive RISC-V UART Device Michael Clark
2018-01-11 2:22 ` [Qemu-devel] [PATCH v3 18/21] SiFive RISC-V PRCI Block Michael Clark
2018-01-11 2:22 ` [Qemu-devel] [PATCH v3 19/21] SiFive Freedom E300 RISC-V Machine Michael Clark
2018-01-12 10:13 ` Antony Pavlov
2018-01-11 2:22 ` [Qemu-devel] [PATCH v3 20/21] SiFive Freedom U500 " Michael Clark
2018-01-11 2:22 ` [Qemu-devel] [PATCH v3 21/21] RISC-V Build Infrastructure Michael Clark
2018-01-11 14:05 ` Eric Blake
2018-01-11 18:43 ` Michael Clark
2018-02-04 21:15 ` Michael Clark
2018-01-11 3:01 ` [Qemu-devel] [PATCH v3 00/21] RISC-V QEMU Port Submission v3 no-reply
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=c97716bd-69fa-c7d5-5e27-af8201e6d999@linaro.org \
--to=richard.henderson@linaro.org \
--cc=kbastian@mail.uni-paderborn.de \
--cc=mjc@sifive.com \
--cc=palmer@sifive.com \
--cc=patches@groups.riscv.org \
--cc=qemu-devel@nongnu.org \
--cc=sagark@eecs.berkeley.edu \
/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).