From: Corey Wharton <coreyw7@fb.com>
To: <qemu-devel@nongnu.org>, <qemu-riscv@nongnu.org>
Cc: Palmer Dabbelt <palmer@dabbelt.com>,
Alistair Francis <Alistair.Francis@wdc.com>,
Sagar Karandikar <sagark@eecs.berkeley.edu>,
Bastian Koppelmann <kbastian@mail.uni-paderborn.de>,
Corey Wharton <coreyw7@fb.com>
Subject: [PATCH 0/2] Support different CPU types for the sifive_e machine
Date: Thu, 12 Mar 2020 17:55:06 -0700 [thread overview]
Message-ID: <20200313005508.1906-1-coreyw7@fb.com> (raw)
The purpose of this patch set is to allow the sifive_e machine to run
with different CPU targets to enable different ISA entensions. To that
end it also introduces a new sifive-e34 CPU type which provides the
same ISA as sifive-e31, with the addition of the single precision
floating-point extension (f). The default CPU for the sifive_e machine
is unchanged.
A user can change the default CPU type by specifying it with the '-cpu'
option on the command line.
Corey Wharton (2):
riscv: sifive_e: Support changing CPU type
target/riscv: Add a sifive-e34 cpu type
hw/riscv/sifive_e.c | 3 ++-
target/riscv/cpu.c | 10 ++++++++++
target/riscv/cpu.h | 1 +
3 files changed, 13 insertions(+), 1 deletion(-)
--
2.21.1
WARNING: multiple messages have this Message-ID (diff)
From: Corey Wharton <coreyw7@fb.com>
To: <qemu-devel@nongnu.org>, <qemu-riscv@nongnu.org>
Cc: Alistair Francis <Alistair.Francis@wdc.com>,
Corey Wharton <coreyw7@fb.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Sagar Karandikar <sagark@eecs.berkeley.edu>,
Bastian Koppelmann <kbastian@mail.uni-paderborn.de>
Subject: [PATCH 0/2] Support different CPU types for the sifive_e machine
Date: Thu, 12 Mar 2020 17:55:06 -0700 [thread overview]
Message-ID: <20200313005508.1906-1-coreyw7@fb.com> (raw)
The purpose of this patch set is to allow the sifive_e machine to run
with different CPU targets to enable different ISA entensions. To that
end it also introduces a new sifive-e34 CPU type which provides the
same ISA as sifive-e31, with the addition of the single precision
floating-point extension (f). The default CPU for the sifive_e machine
is unchanged.
A user can change the default CPU type by specifying it with the '-cpu'
option on the command line.
Corey Wharton (2):
riscv: sifive_e: Support changing CPU type
target/riscv: Add a sifive-e34 cpu type
hw/riscv/sifive_e.c | 3 ++-
target/riscv/cpu.c | 10 ++++++++++
target/riscv/cpu.h | 1 +
3 files changed, 13 insertions(+), 1 deletion(-)
--
2.21.1
next reply other threads:[~2020-03-13 0:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-13 0:55 Corey Wharton [this message]
2020-03-13 0:55 ` [PATCH 0/2] Support different CPU types for the sifive_e machine Corey Wharton
2020-03-13 0:55 ` [PATCH 1/2] riscv: sifive_e: Support changing CPU type Corey Wharton
2020-03-13 0:55 ` Corey Wharton
2020-03-13 14:39 ` Bin Meng
2020-03-13 14:39 ` Bin Meng
2020-03-13 18:32 ` Alistair Francis
2020-03-13 18:32 ` Alistair Francis
2020-03-13 0:55 ` [PATCH 2/2] target/riscv: Add a sifive-e34 cpu type Corey Wharton
2020-03-13 0:55 ` Corey Wharton
2020-03-13 14:42 ` Bin Meng
2020-03-13 14:42 ` Bin Meng
-- strict thread matches above, loose matches on Subject: below --
2020-03-13 0:29 [PATCH 0/2] Support different CPU types for the sifive_e machine Corey Wharton
2020-03-13 0:29 ` Corey Wharton
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=20200313005508.1906-1-coreyw7@fb.com \
--to=coreyw7@fb.com \
--cc=Alistair.Francis@wdc.com \
--cc=kbastian@mail.uni-paderborn.de \
--cc=palmer@dabbelt.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@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 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.