Displaying 20 results from an estimated 30 matches for "_f_".
Did you mean:
_f
2018 Nov 30
4
[PATCH net-next v3 01/13] virtio: add packed ring types and macros
...nsertions(+)
>
> diff --git a/include/uapi/linux/virtio_config.h b/include/uapi/linux/virtio_config.h
> index 449132c76b1c..1196e1c1d4f6 100644
> --- a/include/uapi/linux/virtio_config.h
> +++ b/include/uapi/linux/virtio_config.h
> @@ -75,6 +75,9 @@
> */
> #define VIRTIO_F_IOMMU_PLATFORM 33
>
> +/* This feature indicates support for the packed virtqueue layout. */
> +#define VIRTIO_F_RING_PACKED 34
> +
> /*
> * Does the device support Single Root I/O Virtualization?
> */
> diff --git a/include/uapi/linux/virtio_ring.h b/include/uap...
2018 Nov 30
4
[PATCH net-next v3 01/13] virtio: add packed ring types and macros
...nsertions(+)
>
> diff --git a/include/uapi/linux/virtio_config.h b/include/uapi/linux/virtio_config.h
> index 449132c76b1c..1196e1c1d4f6 100644
> --- a/include/uapi/linux/virtio_config.h
> +++ b/include/uapi/linux/virtio_config.h
> @@ -75,6 +75,9 @@
> */
> #define VIRTIO_F_IOMMU_PLATFORM 33
>
> +/* This feature indicates support for the packed virtqueue layout. */
> +#define VIRTIO_F_RING_PACKED 34
> +
> /*
> * Does the device support Single Root I/O Virtualization?
> */
> diff --git a/include/uapi/linux/virtio_ring.h b/include/uap...
2018 Nov 30
2
[PATCH net-next v3 01/13] virtio: add packed ring types and macros
...6b1c..1196e1c1d4f6 100644
> > > > > > --- a/include/uapi/linux/virtio_config.h
> > > > > > +++ b/include/uapi/linux/virtio_config.h
> > > > > > @@ -75,6 +75,9 @@
> > > > > > */
> > > > > > #define VIRTIO_F_IOMMU_PLATFORM 33
> > > > > > +/* This feature indicates support for the packed virtqueue layout. */
> > > > > > +#define VIRTIO_F_RING_PACKED 34
> > > > > > +
> > > > > > /*
> > > > > > * Does the dev...
2018 Nov 30
2
[PATCH net-next v3 01/13] virtio: add packed ring types and macros
...6b1c..1196e1c1d4f6 100644
> > > > > > --- a/include/uapi/linux/virtio_config.h
> > > > > > +++ b/include/uapi/linux/virtio_config.h
> > > > > > @@ -75,6 +75,9 @@
> > > > > > */
> > > > > > #define VIRTIO_F_IOMMU_PLATFORM 33
> > > > > > +/* This feature indicates support for the packed virtqueue layout. */
> > > > > > +#define VIRTIO_F_RING_PACKED 34
> > > > > > +
> > > > > > /*
> > > > > > * Does the dev...
2018 Nov 30
2
[PATCH net-next v3 01/13] virtio: add packed ring types and macros
...> > > --- a/include/uapi/linux/virtio_config.h
> > > > > > > > +++ b/include/uapi/linux/virtio_config.h
> > > > > > > > @@ -75,6 +75,9 @@
> > > > > > > > */
> > > > > > > > #define VIRTIO_F_IOMMU_PLATFORM 33
> > > > > > > > +/* This feature indicates support for the packed virtqueue layout. */
> > > > > > > > +#define VIRTIO_F_RING_PACKED 34
> > > > > > > > +
> > > > > > > > /*
> >...
2018 Nov 30
2
[PATCH net-next v3 01/13] virtio: add packed ring types and macros
...> > > --- a/include/uapi/linux/virtio_config.h
> > > > > > > > +++ b/include/uapi/linux/virtio_config.h
> > > > > > > > @@ -75,6 +75,9 @@
> > > > > > > > */
> > > > > > > > #define VIRTIO_F_IOMMU_PLATFORM 33
> > > > > > > > +/* This feature indicates support for the packed virtqueue layout. */
> > > > > > > > +#define VIRTIO_F_RING_PACKED 34
> > > > > > > > +
> > > > > > > > /*
> >...
2018 Nov 30
0
[PATCH net-next v3 01/13] virtio: add packed ring types and macros
...> > index 449132c76b1c..1196e1c1d4f6 100644
> > > > > --- a/include/uapi/linux/virtio_config.h
> > > > > +++ b/include/uapi/linux/virtio_config.h
> > > > > @@ -75,6 +75,9 @@
> > > > > */
> > > > > #define VIRTIO_F_IOMMU_PLATFORM 33
> > > > > +/* This feature indicates support for the packed virtqueue layout. */
> > > > > +#define VIRTIO_F_RING_PACKED 34
> > > > > +
> > > > > /*
> > > > > * Does the device support Single Root I...
2018 Nov 30
0
[PATCH net-next v3 01/13] virtio: add packed ring types and macros
...> > > > > > > --- a/include/uapi/linux/virtio_config.h
> > > > > > > +++ b/include/uapi/linux/virtio_config.h
> > > > > > > @@ -75,6 +75,9 @@
> > > > > > > */
> > > > > > > #define VIRTIO_F_IOMMU_PLATFORM 33
> > > > > > > +/* This feature indicates support for the packed virtqueue layout. */
> > > > > > > +#define VIRTIO_F_RING_PACKED 34
> > > > > > > +
> > > > > > > /*
> > > > > >...
2018 Nov 30
0
[PATCH net-next v3 01/13] virtio: add packed ring types and macros
...a/include/uapi/linux/virtio_config.h
> > > > > > > > > +++ b/include/uapi/linux/virtio_config.h
> > > > > > > > > @@ -75,6 +75,9 @@
> > > > > > > > > */
> > > > > > > > > #define VIRTIO_F_IOMMU_PLATFORM 33
> > > > > > > > > +/* This feature indicates support for the packed virtqueue layout. */
> > > > > > > > > +#define VIRTIO_F_RING_PACKED 34
> > > > > > > > > +
> > > > > > > >...
2018 Nov 30
0
[PATCH net-next v3 01/13] virtio: add packed ring types and macros
...git a/include/uapi/linux/virtio_config.h b/include/uapi/linux/virtio_config.h
> > index 449132c76b1c..1196e1c1d4f6 100644
> > --- a/include/uapi/linux/virtio_config.h
> > +++ b/include/uapi/linux/virtio_config.h
> > @@ -75,6 +75,9 @@
> > */
> > #define VIRTIO_F_IOMMU_PLATFORM 33
> > +/* This feature indicates support for the packed virtqueue layout. */
> > +#define VIRTIO_F_RING_PACKED 34
> > +
> > /*
> > * Does the device support Single Root I/O Virtualization?
> > */
> > diff --git a/include/uapi/linux/...
2010 Sep 11
2
[LLVMdev] Valid names for symbols
What's the set of valid characters that can occur in an LLVM symbol name?
The reason I ask is that my compiler is generating symbols based on
method names. Some methods are operators, and I haven't got around to
mangling the names yet. As a result it's producing symbols that look
like _f_+ and _f_:=.
LLVM seems to be coping fine with these so far and the IR output is
quoting them, producing lines like:
%7 = call fastcc i32 @"_f_+"(i8* %6, i32 1)
Should I be mangling the names, or can I rely on LLVM to cope? If so,
will LLVM correctly mangle the names itself to keep the...
2018 Dec 07
1
[RFC 2/3] virtio_ring: add VIRTIO_RING_NO_LEGACY
...ab62..192573827850 100644
> --- a/include/uapi/linux/virtio_ring.h
> +++ b/include/uapi/linux/virtio_ring.h
> @@ -37,6 +37,7 @@
> #include <linux/types.h>
> #include <linux/virtio_types.h>
>
> +#ifndef VIRTIO_RING_NO_LEGACY
> /*
> * Notice: unlike other _F_ flags, below flags are defined as shifted
> * values instead of shifts for compatibility.
> @@ -51,6 +52,7 @@
> #define VRING_USED_F_NO_NOTIFY 1
> /* Same as VRING_SPLIT_AVAIL_F_NO_INTERRUPT. */
> #define VRING_AVAIL_F_NO_INTERRUPT 1
> +#endif /* VIRTIO_RING_NO_LEGACY */
>...
2018 Dec 07
7
[RFC 0/3] virtio_ring: define flags as shifts consistently
This is a follow up of the discussion in this thread:
https://patchwork.ozlabs.org/patch/1001015/#2042353
Tiwei Bie (3):
virtio_ring: define flags as shifts consistently
virtio_ring: add VIRTIO_RING_NO_LEGACY
virtio_ring: use new vring flags
drivers/virtio/virtio_ring.c | 100 ++++++++++++++++++-------------
include/uapi/linux/virtio_ring.h | 61 +++++++++++++------
2 files changed,
2018 Dec 07
7
[RFC 0/3] virtio_ring: define flags as shifts consistently
This is a follow up of the discussion in this thread:
https://patchwork.ozlabs.org/patch/1001015/#2042353
Tiwei Bie (3):
virtio_ring: define flags as shifts consistently
virtio_ring: add VIRTIO_RING_NO_LEGACY
virtio_ring: use new vring flags
drivers/virtio/virtio_ring.c | 100 ++++++++++++++++++-------------
include/uapi/linux/virtio_ring.h | 61 +++++++++++++------
2 files changed,
2017 Apr 13
2
[PATCH v9 5/5] virtio-balloon: VIRTIO_BALLOON_F_MISC_VQ
...g_in;
> +
> + sg_init_one(&sg_in, vb->miscq_in_hdr,
> + sizeof(struct virtio_balloon_miscq_hdr));
> + if (virtqueue_add_inbuf(vb->miscq, &sg_in, 1, vb->miscq_in_hdr,
> + GFP_KERNEL) < 0) {
> + __virtio_clear_bit(vb->vdev,
> + VIRTIO_BALLOON_F_MISC_VQ);
> + dev_warn(&vb->vdev->dev, "%s: add miscq_in_hdr err\n",
> + __func__);
> + return;
> + }
> + virtqueue_kick(vb->miscq);
> +}
> +
> +static void miscq_send_unused_pages(struct virtio_balloon *vb)
> +{
> + struct virtio_balloon_mis...
2017 Apr 13
2
[PATCH v9 5/5] virtio-balloon: VIRTIO_BALLOON_F_MISC_VQ
...g_in;
> +
> + sg_init_one(&sg_in, vb->miscq_in_hdr,
> + sizeof(struct virtio_balloon_miscq_hdr));
> + if (virtqueue_add_inbuf(vb->miscq, &sg_in, 1, vb->miscq_in_hdr,
> + GFP_KERNEL) < 0) {
> + __virtio_clear_bit(vb->vdev,
> + VIRTIO_BALLOON_F_MISC_VQ);
> + dev_warn(&vb->vdev->dev, "%s: add miscq_in_hdr err\n",
> + __func__);
> + return;
> + }
> + virtqueue_kick(vb->miscq);
> +}
> +
> +static void miscq_send_unused_pages(struct virtio_balloon *vb)
> +{
> + struct virtio_balloon_mis...
2018 Sep 07
2
[PATCH net-next v2 1/5] virtio: add packed ring definitions
...insertions(+)
>
> diff --git a/include/uapi/linux/virtio_config.h b/include/uapi/linux/virtio_config.h
> index 449132c76b1c..1196e1c1d4f6 100644
> --- a/include/uapi/linux/virtio_config.h
> +++ b/include/uapi/linux/virtio_config.h
> @@ -75,6 +75,9 @@
> */
> #define VIRTIO_F_IOMMU_PLATFORM 33
>
> +/* This feature indicates support for the packed virtqueue layout. */
> +#define VIRTIO_F_RING_PACKED 34
> +
> /*
> * Does the device support Single Root I/O Virtualization?
> */
> diff --git a/include/uapi/linux/virtio_ring.h b/include/uapi/li...
2018 Sep 07
2
[PATCH net-next v2 1/5] virtio: add packed ring definitions
...insertions(+)
>
> diff --git a/include/uapi/linux/virtio_config.h b/include/uapi/linux/virtio_config.h
> index 449132c76b1c..1196e1c1d4f6 100644
> --- a/include/uapi/linux/virtio_config.h
> +++ b/include/uapi/linux/virtio_config.h
> @@ -75,6 +75,9 @@
> */
> #define VIRTIO_F_IOMMU_PLATFORM 33
>
> +/* This feature indicates support for the packed virtqueue layout. */
> +#define VIRTIO_F_RING_PACKED 34
> +
> /*
> * Does the device support Single Root I/O Virtualization?
> */
> diff --git a/include/uapi/linux/virtio_ring.h b/include/uapi/li...
2010 Sep 11
0
[LLVMdev] Valid names for symbols
...lid characters that can occur in an LLVM symbol name?
>
> The reason I ask is that my compiler is generating symbols based on
> method names. Some methods are operators, and I haven't got around to
> mangling the names yet. As a result it's producing symbols that look
> like _f_+ and _f_:=.
>
> LLVM seems to be coping fine with these so far and the IR output is
> quoting them, producing lines like:
>
> %7 = call fastcc i32 @"_f_+"(i8* %6, i32 1)
>
> Should I be mangling the names, or can I rely on LLVM to cope? If so,
> will LLVM correc...
2017 Apr 27
0
[PATCH v9 5/5] virtio-balloon: VIRTIO_BALLOON_F_MISC_VQ
...n(page);
>> + add_one_chunk(vb, vq,
>> + PAGE_CHUNK_TYPE_UNUSED,
>> + pfn,
>> + (u64)(1 << order));
>> + }
>> + } while (!ret);
>> + }
>> + }
>> + }
>> + miscq_out_hdr->flags |= VIRTIO_BALLOON_MISCQ_F_COMPLETE;
> And where is miscq_out_hdr used? I see no add_outbuf anywhere.
>
> Things like this should be passed through function parameters
> and not stuffed into device structure, fields should be
> initialized before use and not where we happen to
> have the data handy.
>
mi...