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
| ||
|
Date: Fri, 24 Jun 2011 10:14:06 +0900 From: Magnus Damm <magnus.damm@...il.com> To: Bhushan Bharat-R65777 <R65777@...escale.com> Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "vapier@...too.org" <vapier@...too.org>, "mst@...hat.com" <mst@...hat.com>, "linux-sh@...r.kernel.org" <linux-sh@...r.kernel.org>, "virtualization@...ts.linux-foundation.org" <virtualization@...ts.linux-foundation.org> Subject: Re: [PATCH 02/02] virtio: Add virtio platform driver Hi Bhushan Bharat, On Thu, Jun 23, 2011 at 5:54 PM, Bhushan Bharat-R65777 <R65777@...escale.com> wrote: > What purpose this virtio platform driver serves? Are you trying to make driver layers here and each virtio device driver can hook up into this platform driver. Is that correct ? The idea behind the virto platform driver is to have a reusable layer that handles common virtio and vring functionality. Regular virtio drivers for console, network and disk and interfacing to the virtio platform driver, so these paravirtualized drivers can with this virtio platform driver easily be reused by embedded platforms. Vendor specific code is abstracted away from the virtio platform driver and interfaced to using regular interrupts and SoC-specific callbacks. So with this patch virtio can be interfaced as any regular platform driver. This version of the driver is simply reusing the configuration method from lguest. If you want to see all code involved (including extremely experimental backing drivers) then have a look at: http://www.spinics.net/lists/linux-sh/msg07188.html Cheers, / magnus -- 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