qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: Alistair Francis <alistair23@gmail.com>
Cc: Alistair Francis <alistair.francis@wdc.com>,
	"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
	Michael Clark <mjc@sifive.com>,
	Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v1 0/5] riscv: Fix introspection problems
Date: Thu, 19 Jul 2018 09:59:38 +0200	[thread overview]
Message-ID: <d10ee58e-2b2b-7064-ae13-c07ba2040a07@redhat.com> (raw)
In-Reply-To: <CAKmqyKOfS3qKKr8mvVsgcObXKX=6VBAiLG1yHb9DVJhWwWJsPw@mail.gmail.com>

On 18.07.2018 23:31, Alistair Francis wrote:
> On Wed, Jul 18, 2018 at 12:22 AM, Thomas Huth <thuth@redhat.com> wrote:
>> On 17.07.2018 22:27, Alistair Francis wrote:
>>> This is based on Thomas's work fixing introspection problems [1] and
>>> applied to the RISC-V port.
>>>
>>> 1: https://lists.gnu.org/archive/html/qemu-devel/2018-07/msg03261.html
>>>
>>> Alistair Francis (5):
>>>   sifive_e: Fix crash when introspecting the device
>>>   sifive_u: Fix crash when introspecting the device
>>>   virt: Fix crash when introspecting the device
>>>   riscv_hart: Fix crash when introspecting the device
>>>   spike: Fix crash when introspecting the device
>>>
>>>  hw/riscv/riscv_hart.c |  7 +++----
>>>  hw/riscv/sifive_e.c   | 12 ++++++------
>>>  hw/riscv/sifive_u.c   | 15 +++++++--------
>>>  hw/riscv/spike.c      | 10 ++++------
>>>  hw/riscv/virt.c       |  5 ++---
>>>  5 files changed, 22 insertions(+), 27 deletions(-)
>>
>> That's interesting, these issues did not appear in my tests (modified
>> tests/device-introspect-test.c with hmp("info qtree")). Likely because
>> device-introspect-test only checks with the "none" machine ==> one more
>> reason to test here with all machines, too (I suggested such a patch a
>> couple of months ago) ...
> 
> What happened to the patch? More tests would be super handy.

It was only a RFC since at that point in time, there were lots of other
crashes, so it could not be merged yet:

http://lists.gnu.org/archive/html/qemu-devel/2018-03/msg05033.html

I think the other crashes are now fixed, too, so we could consider this
again. I'll put it on my TODO list to respin it for 3.1 ...

 Thomas

  reply	other threads:[~2018-07-19  7:59 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-17 20:27 [Qemu-devel] [PATCH v1 0/5] riscv: Fix introspection problems Alistair Francis
2018-07-17 20:27 ` [Qemu-devel] [PATCH v1 1/5] sifive_e: Fix crash when introspecting the device Alistair Francis
2018-07-17 21:03   ` Michael Clark
2018-07-17 20:28 ` [Qemu-devel] [PATCH v1 2/5] sifive_u: " Alistair Francis
2018-07-17 21:03   ` Michael Clark
2018-07-18 14:11   ` Philippe Mathieu-Daudé
2018-07-17 20:28 ` [Qemu-devel] [PATCH v1 3/5] virt: " Alistair Francis
2018-07-17 21:03   ` Michael Clark
2018-07-17 20:28 ` [Qemu-devel] [PATCH v1 4/5] riscv_hart: " Alistair Francis
2018-07-17 21:04   ` Michael Clark
2018-07-17 20:28 ` [Qemu-devel] [PATCH v1 5/5] spike: " Alistair Francis
2018-07-17 21:04   ` Michael Clark
2018-07-18  7:22 ` [Qemu-devel] [PATCH v1 0/5] riscv: Fix introspection problems Thomas Huth
2018-07-18 21:31   ` Alistair Francis
2018-07-19  7:59     ` Thomas Huth [this message]
2018-07-23 23:13       ` Alistair Francis
2018-07-18  7:23 ` Thomas Huth

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=d10ee58e-2b2b-7064-ae13-c07ba2040a07@redhat.com \
    --to=thuth@redhat.com \
    --cc=alistair.francis@wdc.com \
    --cc=alistair23@gmail.com \
    --cc=armbru@redhat.com \
    --cc=mjc@sifive.com \
    --cc=qemu-devel@nongnu.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).