All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Clark <mjc@sifive.com>
To: DJ Delorie <dj@redhat.com>
Cc: "Richard W.M. Jones" <rjones@redhat.com>,
	"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
	"QEMU Developers" <qemu-devel@nongnu.org>,
	"Palmer Dabbelt" <palmer@sifive.com>,
	"Peter Maydell" <peter.maydell@linaro.org>
Subject: Re: [Qemu-devel] [PATCH v3] RISC-V: Fix riscv_isa_string memory size bug
Date: Thu, 22 Mar 2018 15:21:08 -0700	[thread overview]
Message-ID: <CAHNT7Nsyp+87qfNi=6g9Deqw35nuerv1pYdVAr38X8JpaUFNkQ@mail.gmail.com> (raw)
In-Reply-To: <xnbmfflpqr.fsf@greed.delorie.com>

On Thu, Mar 22, 2018 at 3:17 PM, DJ Delorie <dj@redhat.com> wrote:

> "Richard W.M. Jones" <rjones@redhat.com> writes:
> > DJ, am I remembering correctly that you tried the test case on the
> > HiFive evaluation board and it didn't demonstrate the bug?
>
> I tested it on the vc707 board, without seeing the bug.
>
> I can test other test cases if needed, I've got the board running Fedora
> at the moment.
>

Okay, I'll assume its a QEMU RISC-V bug.

  reply	other threads:[~2018-03-22 22:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-16 17:26 [Qemu-devel] [PATCH v3] RISC-V: Fix riscv_isa_string memory size bug Michael Clark
2018-03-18 23:22 ` Philippe Mathieu-Daudé
2018-03-19 18:35   ` Michael Clark
2018-03-19 19:42     ` Richard W.M. Jones
2018-03-19 21:39       ` Michael Clark
2018-03-22 21:06         ` Michael Clark
2018-03-22 22:09           ` Richard W.M. Jones
2018-03-22 22:17             ` DJ Delorie
2018-03-22 22:21               ` Michael Clark [this message]
2018-03-23 20:01               ` Palmer Dabbelt
2018-03-20  4:43     ` Richard Henderson
2018-03-20 18:06       ` Michael Clark
2018-03-24  4:35         ` Richard Henderson

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='CAHNT7Nsyp+87qfNi=6g9Deqw35nuerv1pYdVAr38X8JpaUFNkQ@mail.gmail.com' \
    --to=mjc@sifive.com \
    --cc=dj@redhat.com \
    --cc=f4bug@amsat.org \
    --cc=palmer@sifive.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=rjones@redhat.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.