From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753251AbZHSQis (ORCPT ); Wed, 19 Aug 2009 12:38:48 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753228AbZHSQiq (ORCPT ); Wed, 19 Aug 2009 12:38:46 -0400 Received: from mx2.redhat.com ([66.187.237.31]:40232 "EHLO mx2.redhat.com" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1753211AbZHSQio (ORCPT ); Wed, 19 Aug 2009 12:38:44 -0400 Message-ID: <4A8C2A87.5060305@redhat.com> Date: Wed, 19 Aug 2009 19:38:31 +0300 From: Avi Kivity User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.1) Gecko/20090814 Fedora/3.0-2.6.b3.fc11 Thunderbird/3.0b3 MIME-Version: 1.0 To: "Ira W. Snyder" CC: "Michael S. Tsirkin" , Gregory Haskins , kvm@vger.kernel.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org, alacrityvm-devel@lists.sourceforge.net, Anthony Liguori , Ingo Molnar , Gregory Haskins , Hollis Blanchard Subject: Re: [Alacrityvm-devel] [PATCH v3 3/6] vbus: add a "vbus-proxy" bus model for vbus_driver objects References: <20090818172752.GC17631@ovro.caltech.edu> <4A8AE918.5000109@redhat.com> <20090818182735.GD17631@ovro.caltech.edu> <4A8AF880.6080704@redhat.com> <20090818205919.GA1168@ovro.caltech.edu> <4A8B1C7F.4060008@redhat.com> <20090819003812.GA11168@ovro.caltech.edu> <4A8B9051.3020505@redhat.com> <20090819152811.GA22294@ovro.caltech.edu> <4A8C1C22.3010101@redhat.com> <20090819162902.GB22294@ovro.caltech.edu> In-Reply-To: <20090819162902.GB22294@ovro.caltech.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 08/19/2009 07:29 PM, Ira W. Snyder wrote: > > >> virtio-$yourhardware or maybe virtio-dma >> >> > How about virtio-phys? > Could work. > Arnd and BenH are both looking at PPC systems (similar to mine). Grant > Likely is looking at talking to an processor core running on an FPGA, > IIRC. Most of the code can be shared, very little should need to be > board-specific, I hope. > Excellent. >>> That said, I'm not sure how qemu-system-ppc running on x86 could >>> possibly communicate using virtio-net. This would mean the guest is an >>> emulated big-endian PPC, while the host is a little-endian x86. I >>> haven't actually tested this situation, so perhaps I am wrong. >>> >>> >> I'm confused now. You don't actually have any guest, do you, so why >> would you run qemu at all? >> >> > I do not run qemu. I am just stating a problem with virtio-net that I > noticed. This is just so someone more knowledgeable can be aware of the > problem. > > Ah, it certainly doesn't byteswap. Maybe nobody tried it. Hollis? -- I have a truly marvellous patch that fixes the bug which this signature is too narrow to contain.