All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Emilio G. Cota" <cota@braap.org>
To: Michael Clark <mjc@sifive.com>
Cc: Stef O'Rear <sorear2@gmail.com>,
	RISC-V Patches <patches@groups.riscv.org>,
	Palmer Dabbelt <palmer@sifive.com>,
	QEMU Developers <qemu-devel@nongnu.org>,
	Sagar Karandikar <sagark@eecs.berkeley.edu>,
	Bastian Koppelmann <kbastian@mail.uni-paderborn.de>
Subject: Re: [Qemu-devel] [patches] Re:  [PULL] RISC-V QEMU Port Submission
Date: Wed, 28 Feb 2018 17:26:27 -0500	[thread overview]
Message-ID: <20180228222627.GA3575@flamenco> (raw)
In-Reply-To: <CAHNT7Nv04hScm7QDtJMhFZeB=WOyOQ6HW1J-xOEO11GM1xFqyA@mail.gmail.com>

On Wed, Feb 28, 2018 at 13:09:11 +1300, Michael Clark wrote:
> BTW somewhat coincidentally, the binary translator I wrote; RV8, which is
> practicaly twice as fast as QEMU only supports privileged ISA v1.9.1 and I
> personally want to keep binary compatiblity with it.
(snip)
> - https://rv8.io/
> - https://rv8.io/bench
> - https://anarch128.org/~mclark/rv8-carrv.pdf
> - https://anarch128.org/~mclark/rv8-slides.pdf

What QEMU versions did you use for those comparisons? I wonder if
the recent indirect branch handling improvements were included in those
(this work was merged in 2.10 for aarch64). Also, 2.7 is quite a bit
faster than previous versions for user-mode due to the use of QHT,
although you probably used a later version.

BTW after the merge you might want to look into optimizing indirect
branches (and cross-page direct jumps in softmmu) for riscv in qemu.
See examples with
	$ git log -Stcg_gen_lookup_and_goto_ptr

Cheers,

		Emilio

  parent reply	other threads:[~2018-02-28 22:26 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-27  0:15 [Qemu-devel] [PULL] RISC-V QEMU Port Submission Michael Clark
2018-02-27 14:01 ` Peter Maydell
2018-02-27 15:50   ` [Qemu-devel] [patches] " Stef O'Rear
2018-02-27 17:50     ` Peter Maydell
2018-02-28  0:21       ` Michael Clark
2018-02-28  0:09     ` Michael Clark
2018-02-28 11:53       ` Peter Maydell
2018-02-28 12:09         ` Peter Maydell
2018-02-28 20:40         ` Michael Clark
2018-03-03  2:09           ` Michael Clark
2018-02-28 22:26       ` Emilio G. Cota [this message]
2018-03-02 13:26         ` Michael Clark
2018-03-05 19:00           ` Emilio G. Cota
2018-03-05 23:31             ` Michael Clark
2018-02-27 16:00   ` [Qemu-devel] " Igor Mammedov
2018-02-28  0:41     ` [Qemu-devel] [patches] " Michael Clark
2018-02-28 10:41       ` Igor Mammedov
2018-02-28  0:34   ` [Qemu-devel] " Michael Clark

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=20180228222627.GA3575@flamenco \
    --to=cota@braap.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 \
    --cc=sorear2@gmail.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 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.