search for: config_virtio_mmio_legacy

...tively disable legacy > or modern macros? > Might be clearer than comments that, after all, never compile. As in, a bunch of #ifdefs disabling the legacy lines of code? Doable, although I'm not sure how beautiful would that be. Will have a look, but it probably would only make sense with CONFIG_VIRTIO_MMIO_LEGACY option. Pawe?

...tively disable legacy > or modern macros? > Might be clearer than comments that, after all, never compile. As in, a bunch of #ifdefs disabling the legacy lines of code? Doable, although I'm not sure how beautiful would that be. Will have a look, but it probably would only make sense with CONFIG_VIRTIO_MMIO_LEGACY option. Pawe?

...> > Might be clearer than comments that, after all, never compile. > > > > As in, a bunch of #ifdefs disabling the legacy lines of code? Doable, > > although I'm not sure how beautiful would that be. Will have a look, but > > it probably would only make sense with CONFIG_VIRTIO_MMIO_LEGACY option. > > > > Pawe? > > Not necessarily - the point is for userspace to be able to > avoid getting useless legacy macros by means of a simple #define. > Again, take a look at my tree: > > git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git vhost-next I ha...

...> > Might be clearer than comments that, after all, never compile. > > > > As in, a bunch of #ifdefs disabling the legacy lines of code? Doable, > > although I'm not sure how beautiful would that be. Will have a look, but > > it probably would only make sense with CONFIG_VIRTIO_MMIO_LEGACY option. > > > > Pawe? > > Not necessarily - the point is for userspace to be able to > avoid getting useless legacy macros by means of a simple #define. > Again, take a look at my tree: > > git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git vhost-next I ha...

...; or modern macros? > > Might be clearer than comments that, after all, never compile. > > As in, a bunch of #ifdefs disabling the legacy lines of code? Doable, > although I'm not sure how beautiful would that be. Will have a look, but > it probably would only make sense with CONFIG_VIRTIO_MMIO_LEGACY option. > > Pawe? Not necessarily - the point is for userspace to be able to avoid getting useless legacy macros by means of a simple #define. Again, take a look at my tree: git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git vhost-next -- MST

...; or modern macros? > > Might be clearer than comments that, after all, never compile. > > As in, a bunch of #ifdefs disabling the legacy lines of code? Doable, > although I'm not sure how beautiful would that be. Will have a look, but > it probably would only make sense with CONFIG_VIRTIO_MMIO_LEGACY option. > > Pawe? Not necessarily - the point is for userspace to be able to avoid getting useless legacy macros by means of a simple #define. Again, take a look at my tree: git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git vhost-next -- MST

...learer than comments that, after all, never compile. > > > > > > As in, a bunch of #ifdefs disabling the legacy lines of code? Doable, > > > although I'm not sure how beautiful would that be. Will have a look, but > > > it probably would only make sense with CONFIG_VIRTIO_MMIO_LEGACY option. > > > > > > Pawe? > > > > Not necessarily - the point is for userspace to be able to > > avoid getting useless legacy macros by means of a simple #define. > > Again, take a look at my tree: > > > > git://git.kernel.org/pub/scm/linux/k...

...learer than comments that, after all, never compile. > > > > > > As in, a bunch of #ifdefs disabling the legacy lines of code? Doable, > > > although I'm not sure how beautiful would that be. Will have a look, but > > > it probably would only make sense with CONFIG_VIRTIO_MMIO_LEGACY option. > > > > > > Pawe? > > > > Not necessarily - the point is for userspace to be able to > > avoid getting useless legacy macros by means of a simple #define. > > Again, take a look at my tree: > > > > git://git.kernel.org/pub/scm/linux/k...

This patch add a support for second version of the virtio-mmio device, which follows OASIS "Virtual I/O Device (VIRTIO) Version 1.0" specification. Main changes: 1. The control register symbolic names use the new device/driver nomenclature rather than the old guest/host one. 2. The driver detect the device version (version 1 is the pre-OASIS spec, version 2 is compatible with

This patch add a support for second version of the virtio-mmio device, which follows OASIS "Virtual I/O Device (VIRTIO) Version 1.0" specification. Main changes: 1. The control register symbolic names use the new device/driver nomenclature rather than the old guest/host one. 2. The driver detect the device version (version 1 is the pre-OASIS spec, version 2 is compatible with