lkml.org 
[lkml]   [2015]   [Feb]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH 4/5] virtio: Don't expose legacy config features when VIRTIO_CONFIG_NO_LEGACY defined.
On Fri, Feb 06, 2015 at 03:36:55PM +1030, Rusty Russell wrote:
> The VIRTIO_F_ANY_LAYOUT and VIRTIO_F_NOTIFY_ON_EMPTY features are pre-1.0
> only.
>
> Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>

Acked-by: Michael S. Tsirkin <mst@redhat.com>

> ---
> include/uapi/linux/virtio_config.h | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/include/uapi/linux/virtio_config.h b/include/uapi/linux/virtio_config.h
> index a6d0cdeaacd4..c18264df9504 100644
> --- a/include/uapi/linux/virtio_config.h
> +++ b/include/uapi/linux/virtio_config.h
> @@ -49,12 +49,14 @@
> #define VIRTIO_TRANSPORT_F_START 28
> #define VIRTIO_TRANSPORT_F_END 33
>
> +#ifndef VIRTIO_CONFIG_NO_LEGACY
> /* Do we get callbacks when the ring is completely used, even if we've
> * suppressed them? */
> #define VIRTIO_F_NOTIFY_ON_EMPTY 24
>
> /* Can the device handle any descriptor layout? */
> #define VIRTIO_F_ANY_LAYOUT 27
> +#endif /* VIRTIO_CONFIG_NO_LEGACY */
>
> /* v1.0 compliant. */
> #define VIRTIO_F_VERSION_1 32
> --
> 2.1.0


\
 
 \ /
  Last update: 2015-02-08 12:21    [W:0.095 / U:3.664 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site