qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
To: Reinoud Zandijk <reinoud@NetBSD.org>,
	Aleksandar Rikalo <aleksandar.rikalo@syrmia.com>
Cc: Thomas Huth <thuth@redhat.com>,
	Huacai Chen <chenhuacai@kernel.org>,
	qemu-devel@nongnu.org
Subject: Re: RFC Qemu mipssim patches
Date: Fri, 12 Feb 2021 01:13:22 +0100	[thread overview]
Message-ID: <acf26892-c47c-7059-f3d1-8ef5bdcdcb8b@amsat.org> (raw)
In-Reply-To: <20210211153746.GA25676@dropje.13thmonkey.org>

Hi Reinoud,

On 2/11/21 4:37 PM, Reinoud Zandijk wrote:
> Hi,
> 
> i'd like to get the following simple patches to the MIPS/mipssim target adding
> virtio-mmio devices to it. This makes the target a lot more usefull as microvm
> for kernel developement. It currently lives in our qemu extensions patches and
> we have a working kernel that supports all virtio devices for it.
> 
> Thoughts?

Why not start a cleanly specified machine, as Laurent is doing on m68k?
https://www.mail-archive.com/qemu-devel@nongnu.org/msg768802.html

This one doesn't even have an interrupt controller.

Cc'ing Aleksandar who maintains this machine.

Regards,

Phil.


  reply	other threads:[~2021-02-12  0:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-11 15:37 RFC Qemu mipssim patches Reinoud Zandijk
2021-02-12  0:13 ` Philippe Mathieu-Daudé [this message]
2021-02-12  9:44   ` Philippe Mathieu-Daudé
2021-02-13 10:05     ` Qemu mipssim patches, mips malta and virtio bugs Reinoud Zandijk
2021-02-13 13:14       ` Philippe Mathieu-Daudé
2021-02-15  6:39         ` Thomas Huth
2021-02-15  7:56           ` Philippe Mathieu-Daudé

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=acf26892-c47c-7059-f3d1-8ef5bdcdcb8b@amsat.org \
    --to=f4bug@amsat.org \
    --cc=aleksandar.rikalo@syrmia.com \
    --cc=chenhuacai@kernel.org \
    --cc=qemu-devel@nongnu.org \
    --cc=reinoud@NetBSD.org \
    --cc=thuth@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 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).