From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:60443) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QPJJt-0004Gb-BX for qemu-devel@nongnu.org; Wed, 25 May 2011 15:00:38 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QPJJs-0008W8-IX for qemu-devel@nongnu.org; Wed, 25 May 2011 15:00:37 -0400 Received: from mail-pz0-f45.google.com ([209.85.210.45]:33813) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QPJJs-0008Vr-E8 for qemu-devel@nongnu.org; Wed, 25 May 2011 15:00:36 -0400 Received: by pzk30 with SMTP id 30so4199349pzk.4 for ; Wed, 25 May 2011 12:00:35 -0700 (PDT) Message-ID: <4DDD51CD.3050909@mcgary.org> Date: Wed, 25 May 2011 12:00:29 -0700 From: Greg McGary MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Virtio net bringup for new arch? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org 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