[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090219170313.GC12795@ovro.caltech.edu>
Date: Thu, 19 Feb 2009 09:03:14 -0800
From: Ira Snyder <iws@...o.caltech.edu>
To: Kumar Gala <galak@...nel.crashing.org>
Cc: Zang Roy-R61911 <tie-fei.zang@...escale.com>,
Arnd Bergmann <arnd@...db.de>,
Jan-Bernd Themann <THEMANN@...ibm.com>, netdev@...r.kernel.org,
Rusty Russell <rusty@...tcorp.com.au>,
linux-kernel@...r.kernel.org, linuxppc-dev@...abs.org
Subject: Re: [RFC v1] virtio: add virtio-over-PCI driver
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@...abs.org
>>> [mailto:linuxppc-dev-bounces+tie-fei.zang=freescale.com@...abs
>>> .org] On Behalf Of Kumar Gala
>>> Sent: Thursday, February 19, 2009 0:47 AM
>>> To: Ira Snyder
>>> Cc: Arnd Bergmann; Jan-Bernd Themann; netdev@...r.kernel.org;
>>> Rusty Russell; linux-kernel@...r.kernel.org; linuxppc-dev@...abs.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists