From: Greg McGary <greg.mcgary@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Virtio net bringup for new arch?
Date: Wed, 25 May 2011 12:00:29 -0700 [thread overview]
Message-ID: <4DDD51CD.3050909@mcgary.org> (raw)
I have a new architecture port that can boot linux and work interactively with a UART.
The next step to facilitate application development is to have NFS filesystems. The
real HW has no bus--it will have some sort of shared-memory, SW-arbitrated access to a
control processor's devices. For development on QEMU, I'm guessing the easiest way to
fake a network is to use virtio-net, since linux kernel and QEMU both support it.
Perhaps when it comes time to implement the network link to the control-processor,
virtio-net will be the best choice there as well.
Now, I need to know how to glue it all together. Questions:
* the Syborg virtual board seemed like a good & simple reference; but unfortunately,
I can't find a full set of system and userspace software to get it running. Any
leads here?
* Even though there is no bus, does it make sense to pretend there is a PCI bus?
I had the idea that this might be the quickest bringup, since it would require
minimal porting on the kernel side: QEMU populates the PCI config space with the
virtio-net device and Linux auto-detects at boot. If it's equivalent effort to
configure and connect the virtio-net device directly, I'd rather not pretend PCI.
All ideas, leads and advice gratefully accepted.
G
next reply other threads:[~2011-05-25 19:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-25 19:00 Greg McGary [this message]
2011-05-25 20:10 ` [Qemu-devel] Virtio net bringup for new arch? Alexander Graf
2011-05-25 20:22 ` Greg McGary
2011-05-25 20:48 ` Alexander Graf
2011-05-25 21:33 ` 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=4DDD51CD.3050909@mcgary.org \
--to=greg.mcgary@gmail.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).