qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
* [Qemu-devel] Virtio net bringup for new arch?
@ 2011-05-25 19:00 Greg McGary
  2011-05-25 20:10 ` Alexander Graf
  0 siblings, 1 reply; 5+ messages in thread
From: Greg McGary @ 2011-05-25 19:00 UTC (permalink / raw)
  To: qemu-devel

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

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2011-05-25 21:33 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-05-25 19:00 [Qemu-devel] Virtio net bringup for new arch? Greg McGary
2011-05-25 20:10 ` Alexander Graf
2011-05-25 20:22   ` Greg McGary
2011-05-25 20:48     ` Alexander Graf
2011-05-25 21:33     ` Richard Henderson

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).