linux-kernel - Re: [RFC v3] arm: Add platform bus driver for memory mapped virtio device

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <874o09ryzm.fsf@rustcorp.com.au>
Date:	Mon, 19 Sep 2011 12:59:33 +0930
From:	Rusty Russell <rusty@...tcorp.com.au>
To:	Anthony Liguori <aliguori@...ibm.com>,
	Pawel Moll <pawel.moll@....com>
Cc:	linux-kernel@...r.kernel.org,
	virtualization@...ts.linux-foundation.org,
	linux-arm-kernel@...ts.infradead.org,
	"Michael S.Tsirkin" <mst@...hat.com>
Subject: Re: [RFC v3] arm: Add platform bus driver for memory mapped virtio device

On Fri, 16 Sep 2011 12:01:49 -0500, Anthony Liguori <aliguori@...ibm.com> wrote:
> On 09/16/2011 11:47 AM, Pawel Moll wrote:
> > This patch, based on virtio PCI driver, adds support for memory
> > mapped (platform) virtio  device. This should allow environments
> > like qemu to use virtio-based block&  network devices.
> >
> > One can define and register a platform device which resources
> > will describe memory mapped control registers and "mailbox"
> > interrupt. Such device can be also instantiated using the Device
> > Tree node with compatible property equal "virtio,mmio".
> >
> > Cc: Rusty Russell<rusty@...tcorp.com.au>
> > Cc: Anthony Liguori<aliguori@...ibm.com>
> > Cc: Michael S.Tsirkin<mst@...hat.com>
> > Signed-off-by: Pawel Moll<pawel.moll@....com>
> 
> Have you written a specification for this device?
> 
> Rusty maintains a formal spec for all virtio devices at:
> 
> http://ozlabs.org/~rusty/virtio-spec/
> 
> The spec should be written before merging the code to make sure that there 
> aren't future compatibility problems.

A good idea, but the current spec is for PCI.  I wonder if we should
move the PCI part out to an appendix and make it more general?

Meanwhile, perhaps this would be suitable as an appendix.

Cheers,
Rusty.
--
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/