[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87zk4ye2jz.fsf@rustcorp.com.au>
Date: Mon, 10 Sep 2012 17:23:52 +0930
From: Rusty Russell <rusty@...tcorp.com.au>
To: sjur.brandeland@...ricsson.com,
"Michael S . Tsirkin" <mst@...hat.com>
Cc: Sjur Brændeland <sjurbren@...il.com>,
Sjur Brændeland <sjur.brandeland@...ricsson.com>,
Amit Shah <amit.shah@...hat.com>,
Ohad Ben-Cohen <ohad@...ery.com>,
Linus Walleij <linus.walleij@...aro.org>,
virtualization@...ts.linux-foundation.org,
linux-kernel@...r.kernel.org
Subject: Re: [RFCv2 1/2] virtio_console: Add support for DMA memory allocation
sjur.brandeland@...ricsson.com writes:
> From: Sjur Brændeland <sjur.brandeland@...ricsson.com>
>
> Add feature VIRTIO_CONSOLE_F_DMA_MEM. If the architecture has
> DMA support and this feature bit is set, the virtio data buffers
> will be allocated from DMA memory. If the device requests
> the feature VIRTIO_CONSOLE_F_DMA_MEM, but the architecture
> don't support DMA the driver's probe function will fail.
>
> This is needed for using virtio_console from the remoteproc
> framework.
Sorry for the back and forth, I've been pondering MST's points.
If we make a new dma-multiport device (eg. ID 11), how ugly is the code?
It would be a virtio console with DMA buffers and no console, just the
multiport stuff. This would have no impact on the current spec for
virtio console.
Thanks,
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/
Powered by blists - more mailing lists