virtio gpu sparse warning

From	"Michael S. Tsirkin" <mst@redhat.com>
Newsgroups	linux.kernel
Subject	virtio gpu sparse warning
Date	2016-11-24 04:00 +0100
Message-ID	<sGSqt-4QG-3@gated-at.bofh.it> (permalink)
References	<sAUll-4ZD-37@gated-at.bofh.it> <sBllw-5TP-25@gated-at.bofh.it> <sBw7f-4HJ-15@gated-at.bofh.it> <sCmSd-6F5-19@gated-at.bofh.it> <sE8i6-3kM-1@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

sparse produces these warnings:

drivers/gpu/drm/virtio/virtgpu_fb.c:340:27: warning: incorrect type in
assignment (different address spaces)
drivers/gpu/drm/virtio/virtgpu_fb.c:340:27:    expected char [noderef]
<asn:2>*screen_base
drivers/gpu/drm/virtio/virtgpu_fb.c:340:27:    got void *vmap

This is because the expected type is void __iomem *, while
virtio gpu object is void *vmap.

We could just cast the warning away but I'm not sure this
is not a symptom of an actual problem. For example, might
some code call iounmap on this address?

-- 
MST

Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

Re: BUG: 'list_empty(&vgdev->free_vbufs)' is true! Gerd Hoffmann <kraxel@redhat.com> - 2016-11-16 14:20 +0100
  virtio gpu sparse warning "Michael S. Tsirkin" <mst@redhat.com> - 2016-11-24 04:00 +0100

csiph-web