On 26 April 2013 17:03, Peter Maydell <peter.mayd...@linaro.org> wrote: > On 26 April 2013 12:19, Alexander Graf <ag...@suse.de> wrote: >> MMIO registers are handled by a different layer than the virtio >> console itself. After the virtio refactoring in QEMU, they will >> be completely separate drivers. > > Good point -- we don't really want to be mixing up the > transport and the backend. You can see it in the kvmtool > patch, in fact -- it introduces an "if this is virtio-console" > special case into the mmio.c file which previously was > entirely backend agnostic.
Well, we can always have virtio device specific config registers handle by virtio device backends and generic virtio config register handled by transport. kvmtool patch is hacky because it does not provide virtio device specific config read/write callbacks. > > thanks > -- PMM > _______________________________________________ > kvmarm mailing list > kvm...@lists.cs.columbia.edu > https://lists.cs.columbia.edu/cucslists/listinfo/kvmarm --Anup -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
