From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Oleksandr Andrushchenko <andr2000@gmail.com>,
xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org, linux-media@vger.kernel.org,
jgross@suse.com, konrad.wilk@oracle.com
Cc: daniel.vetter@intel.com, dongwon.kim@intel.com,
matthew.d.roper@intel.com,
Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>
Subject: Re: [PATCH v5 0/8] xen: dma-buf support for grant device
Date: Fri, 20 Jul 2018 10:08:36 -0400 [thread overview]
Message-ID: <019c0eb6-8185-d888-ae6f-305ea2d44124@oracle.com> (raw)
In-Reply-To: <20180720090150.24560-1-andr2000@gmail.com>
On 07/20/2018 05:01 AM, Oleksandr Andrushchenko wrote:
> From: Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>
>
> This work is in response to my previous attempt to introduce Xen/DRM
> zero-copy driver [1] to enable Linux dma-buf API [2] for Xen based
> frontends/backends. There is also an existing hyper_dmabuf approach
> available [3] which, if reworked to utilize the proposed solution,
> can greatly benefit as well.
Lot of warnings on i386 build:
In file included from
/data/upstream/linux-xen/drivers/gpu/drm/xen/xen_drm_front.c:24:
/data/upstream/linux-xen/drivers/gpu/drm/xen/xen_drm_front.h: In
function ‘xen_drm_front_fb_to_cookie’:
/data/upstream/linux-xen/drivers/gpu/drm/xen/xen_drm_front.h:129:9:
warning: cast from pointer to integer of different size
[-Wpointer-to-int-cast]
return (u64)fb;
^
/data/upstream/linux-xen/drivers/gpu/drm/xen/xen_drm_front.h: In
function ‘xen_drm_front_dbuf_to_cookie’:
/data/upstream/linux-xen/drivers/gpu/drm/xen/xen_drm_front.h:134:9:
warning: cast from pointer to integer of different size
[-Wpointer-to-int-cast]
return (u64)gem_obj;
^
CC [M] net/netfilter/ipset/ip_set_hash_ipport.o
CC drivers/media/rc/keymaps/rc-tango.o
CC [M] drivers/gpu/drm/vmwgfx/vmwgfx_fifo.o
AR drivers/misc/built-in.a
In file included from
/data/upstream/linux-xen/drivers/gpu/drm/xen/xen_drm_front_kms.c:20:
/data/upstream/linux-xen/drivers/gpu/drm/xen/xen_drm_front.h: In
function ‘xen_drm_front_fb_to_cookie’:
CC [M] drivers/gpu/drm/xen/xen_drm_front_conn.o
/data/upstream/linux-xen/drivers/gpu/drm/xen/xen_drm_front.h:129:9:
warning: cast from pointer to integer of different size
[-Wpointer-to-int-cast]
return (u64)fb;
(and more)
and then
data/upstream/linux-xen/drivers/xen/gntdev-dmabuf.c: In function
‘gntdev_ioctl_dmabuf_exp_from_refs’:
/data/upstream/linux-xen/drivers/xen/gntdev-dmabuf.c:503:6: warning:
‘args.fd’ may be used uninitialized in this function [-Wmaybe-uninitialized]
*fd = args.fd;
~~~~^~~~~~~~~
/data/upstream/linux-xen/drivers/xen/gntdev-dmabuf.c:467:35: note:
‘args.fd’ was declared here
struct gntdev_dmabuf_export_args args;
^~~~
-boris
next prev parent reply other threads:[~2018-07-20 14:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-20 9:01 Oleksandr Andrushchenko
2018-07-20 9:01 ` [PATCH v5 1/8] xen/grant-table: Make set/clear page private code shared Oleksandr Andrushchenko
2018-07-20 9:01 ` [PATCH v5 2/8] xen/balloon: Share common memory reservation routines Oleksandr Andrushchenko
2018-07-20 9:01 ` [PATCH v5 3/8] xen/grant-table: Allow allocating buffers suitable for DMA Oleksandr Andrushchenko
2018-07-20 9:01 ` [PATCH v5 4/8] xen/gntdev: Allow mappings for DMA buffers Oleksandr Andrushchenko
2018-07-20 9:01 ` [PATCH v5 5/8] xen/gntdev: Make private routines/structures accessible Oleksandr Andrushchenko
2018-07-20 9:01 ` [PATCH v5 6/8] xen/gntdev: Add initial support for dma-buf UAPI Oleksandr Andrushchenko
2018-07-20 9:01 ` [PATCH v5 7/8] xen/gntdev: Implement dma-buf export functionality Oleksandr Andrushchenko
2018-07-20 9:01 ` [PATCH v5 8/8] xen/gntdev: Implement dma-buf import functionality Oleksandr Andrushchenko
2018-07-20 14:08 ` Boris Ostrovsky [this message]
2018-07-23 8:38 ` [PATCH v5 0/8] xen: dma-buf support for grant device Oleksandr Andrushchenko
2018-07-23 13:26 ` Oleksandr Andrushchenko
2018-07-23 15:22 ` Boris Ostrovsky
2018-07-23 15:50 ` Oleksandr Andrushchenko
2018-07-23 15:16 ` Boris Ostrovsky
2018-07-31 17:04 ` Boris Ostrovsky
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=019c0eb6-8185-d888-ae6f-305ea2d44124@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=andr2000@gmail.com \
--cc=daniel.vetter@intel.com \
--cc=dongwon.kim@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jgross@suse.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=matthew.d.roper@intel.com \
--cc=oleksandr_andrushchenko@epam.com \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®