From: Paolo Bonzini <pbonzini@redhat.com>
To: KONRAD Frederic <frederic.konrad@adacore.com>,
QEMU Developers <qemu-devel@nongnu.org>,
sw-dev@groups.riscv.org
Cc: kbastian@mail.uni-paderborn.de
Subject: Re: [Qemu-devel] RFC: qemu RISC-V
Date: Wed, 23 Aug 2017 22:29:14 +0200 [thread overview]
Message-ID: <3cf9e9c9-3320-46c2-b8d7-2e77986863d4@redhat.com> (raw)
In-Reply-To: <d2c54be0-8eec-9b6f-63e3-c31e487bc7f3@adacore.com>
On 23/08/2017 21:25, KONRAD Frederic wrote:
> Hi all,
>
> I found somes slides about RISC-V at the KVM forum 2016.
>
> Seems the upstreaming process should have started in september 2016 but
> I didn't see anything.
>
> Is that still planed?
We're waiting from the privileged interface specification to become stable.
The linux-user emulation could go in now (for some value of now), but
the RISC-V people wanted to have the system emulation first.
Paolo
next prev parent reply other threads:[~2017-08-23 20:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-23 19:25 [Qemu-devel] RFC: qemu RISC-V KONRAD Frederic
2017-08-23 20:29 ` Paolo Bonzini [this message]
2017-08-25 11:02 ` KONRAD Frederic
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=3cf9e9c9-3320-46c2-b8d7-2e77986863d4@redhat.com \
--to=pbonzini@redhat.com \
--cc=frederic.konrad@adacore.com \
--cc=kbastian@mail.uni-paderborn.de \
--cc=qemu-devel@nongnu.org \
--cc=sw-dev@groups.riscv.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 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).