mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Ira W. Snyder" <iws@ovro.caltech.edu>
To: Magnus Damm <magnus.damm@gmail.com>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
	linux-s390@vger.kernel.org,
	virtualization@lists.linux-foundation.org, mst@redhat.com,
	linux-kernel@vger.kernel.org, linux-sh@vger.kernel.org
Subject: Re: [PATCH 00/02] virtio: Virtio platform driver
Date: Wed, 16 Mar 2011 08:40:47 -0700	[thread overview]
Message-ID: <20110316154047.GB21758@ovro.caltech.edu> (raw)
In-Reply-To: <AANLkTi=zjGubKx0vV+hqEYiVFVNTAEoGwxEfL4oprxk8@mail.gmail.com>

On Wed, Mar 16, 2011 at 02:17:15PM +0900, Magnus Damm wrote:
> Hi Rusty,
> 
> On Wed, Mar 16, 2011 at 12:46 PM, Rusty Russell <rusty@rustcorp.com.au> wrote:
> > On Thu, 10 Mar 2011 16:05:41 +0900, Magnus Damm <magnus.damm@gmail.com> wrote:
> >> virtio: Virtio platform driver
> >>
> >> [PATCH 01/02] virtio: Break out lguest virtio code to virtio_lguest.c
> >> [PATCH 02/02] virtio: Add virtio platform driver
> >
> > I have no problem with these patches, but it's just churn until we see
> > your actual drivers.
> 
> Well, actually this platform driver is used together with already
> existing drivers, so there are no new virtio drivers to wait for.
> 
> The drivers that have been tested are so far:
> 
> CONFIG_VIRTIO_CONSOLE=y
> CONFIG_VIRTIO_NET=y
> 
> At this point there are four different pieces of code working together
> 
> 1) Virtio platform driver patches (for guest)
> 2) SH4AL-DSP guest kernel patch
> 3) ARM UIO driver patches (for host)
> 4) User space backing code for ARM based on lguest.c
> 
> These patches in this mail thread are 1), and I decided to brush up
> that portion and submit upstream because it's the part that is easiest
> to break out. I intend to post the rest bit by bit over time, but if
> someone is interested then I can post everything at once too.
> 

I'm very interested in the full series of patches. I want to do
something similar to talk between two Linux kernels (x86 and PowerPC)
connected by a PCI bus.

Thanks,
Ira

> > The S/390 devs might be interested, as their bus is very similar too...
> 
> The lguest device code is very similar as well, perhaps it's worth
> refactoring that a bit to build on top of the platform driver. Not
> sure if you see that as a move in the right direction though.
> 
> Thanks for your feedback!
> 
> / magnus
> _______________________________________________
> Virtualization mailing list
> Virtualization@lists.linux-foundation.org
> https://lists.linux-foundation.org/mailman/listinfo/virtualization

  reply	other threads:[~2011-03-16 15:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-10  7:05 Magnus Damm
2011-03-10  7:05 ` [PATCH 01/02] virtio: Break out lguest virtio code to virtio_lguest.c Magnus Damm
2011-03-10  7:06 ` [PATCH 02/02] virtio: Add virtio platform driver Magnus Damm
2011-03-16  3:46 ` [PATCH 00/02] virtio: Virtio " Rusty Russell
2011-03-16  5:17   ` Magnus Damm
2011-03-16 15:40     ` Ira W. Snyder [this message]
2011-03-17  6:50       ` Magnus Damm

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=20110316154047.GB21758@ovro.caltech.edu \
    --to=iws@ovro.caltech.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=mst@redhat.com \
    --cc=rusty@rustcorp.com.au \
    --cc=virtualization@lists.linux-foundation.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

all inboxes | Powered by JetHome®