From: Ira Snyder <iws@ovro.caltech.edu>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: Zang Roy-R61911 <tie-fei.zang@freescale.com>,
Arnd Bergmann <arnd@arndb.de>,
Jan-Bernd Themann <THEMANN@de.ibm.com>,
netdev@vger.kernel.org, Rusty Russell <rusty@rustcorp.com.au>,
linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org
Subject: Re: [RFC v1] virtio: add virtio-over-PCI driver
Date: Thu, 19 Feb 2009 09:03:14 -0800 [thread overview]
Message-ID: <20090219170313.GC12795@ovro.caltech.edu> (raw)
In-Reply-To: <C04B22C6-BCE8-4D99-A160-22F8846C8209@kernel.crashing.org>
On Thu, Feb 19, 2009 at 10:51:43AM -0600, Kumar Gala wrote:
>
> On Feb 19, 2009, at 12:13 AM, Zang Roy-R61911 wrote:
>
>>
>>
>>> -----Original Message-----
>>> From:
>>> linuxppc-dev-bounces+tie-fei.zang=freescale.com@ozlabs.org
>>> [mailto:linuxppc-dev-bounces+tie-fei.zang=freescale.com@ozlabs
>>> .org] On Behalf Of Kumar Gala
>>> Sent: Thursday, February 19, 2009 0:47 AM
>>> To: Ira Snyder
>>> Cc: Arnd Bergmann; Jan-Bernd Themann; netdev@vger.kernel.org;
>>> Rusty Russell; linux-kernel@vger.kernel.org; linuxppc-dev@ozlabs.org
>>> Subject: Re: [RFC v1] virtio: add virtio-over-PCI driver
>>>
>>>
>>> On Feb 17, 2009, at 4:24 PM, Ira Snyder wrote:
>>>
>>>>
>>>> Documentation/virtio-over-PCI.txt | 61 ++
>>>> arch/powerpc/boot/dts/mpc834x_mds.dts | 7 +
>>>
>>> we'll have to review the .dts and expect a documentation update for
>>> the node. But that's pretty minor at this point.
>>>
>>>> drivers/virtio/Kconfig | 22 +
>>>> drivers/virtio/Makefile | 2 +
>>>> drivers/virtio/vop.h | 119 ++
>>>> drivers/virtio/vop_fsl.c | 1911
>>> ++++++++++++++++++++++++
>>>> +++++++++
>>>
>>> make this vop_fsl_mpc83xx.c or something along those lines.
>> why?
>
> so we can deal with 85xx as well. We just need to isolate the 83xx
> specific bits (message usage)
>
In fact, most of the driver has nothing to do with hardware, and
everything to do with managing memory.
Most of the driver could be shared between implementations. The only
things that would be hardware specific are setting up the descriptor
memory, and raising/handling interrupts.
I just wanted to get something working and out here to discuss. I
figured that more hardware support, features, etc. could come later.
Just like everything else in the kernel, I'm sure this will have to
evolve over time as well.
Thanks,
Ira
next prev parent reply other threads:[~2009-02-19 17:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-17 22:24 [RFC v1] virtio: add virtio-over-PCI driver Ira Snyder
2009-02-18 6:43 ` Rusty Russell
2009-02-18 16:38 ` Ira Snyder
2009-02-19 11:18 ` Rusty Russell
2009-02-19 16:49 ` Ira Snyder
2009-02-18 16:47 ` Kumar Gala
2009-02-19 6:13 ` Zang Roy-R61911
2009-02-19 16:51 ` Kumar Gala
2009-02-19 17:03 ` Ira Snyder [this message]
2009-02-20 3:44 ` Zang Roy-R61911
2009-02-19 6:10 ` Zang Roy-R61911
2009-02-19 16:14 ` Ira Snyder
2009-02-20 3:37 ` Zang Roy-R61911
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=20090219170313.GC12795@ovro.caltech.edu \
--to=iws@ovro.caltech.edu \
--cc=THEMANN@de.ibm.com \
--cc=arnd@arndb.de \
--cc=galak@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=tie-fei.zang@freescale.com \
/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).