From: Thomas Hellstrom <thellstrom@vmware.com>
To: Colin King <colin.king@canonical.com>,
VMware Graphics <linux-graphics-maintainer@vmware.com>,
Sinclair Yeh <syeh@vmware.com>, David Airlie <airlied@linux.ie>,
dri-devel@lists.freedesktop.org
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/vmwgfx: remove DRM_ERROR message, stops log spamming
Date: Tue, 12 Sep 2017 19:42:02 +0200 [thread overview]
Message-ID: <211c7afe-c778-cf39-760a-05bc3a62e5db@vmware.com> (raw)
In-Reply-To: <20170912173530.14132-1-colin.king@canonical.com>
Hi, Colin,
On 09/12/2017 07:35 PM, Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> mmap'ing the device multiple times will spam the kernel log with the
> DRM_ERROR message about illegal mmap'ing the old fifo space.
How are you hitting this? Multiple mappings should be fine as long as
mapping offsets are correct,
so hitting this message should indicate that the user-space app is doing
something seriously wrong, and
having it present in the log should probably help more than it hurts.
/Thomas
> Since
> the mmap'ing will fail with an -EINVAL there is no need to emit this
> message, so just remove it.
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
> ---
> drivers/gpu/drm/vmwgfx/vmwgfx_ttm_glue.c | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/vmwgfx/vmwgfx_ttm_glue.c b/drivers/gpu/drm/vmwgfx/vmwgfx_ttm_glue.c
> index e771091d2cd3..1e633c602fb1 100644
> --- a/drivers/gpu/drm/vmwgfx/vmwgfx_ttm_glue.c
> +++ b/drivers/gpu/drm/vmwgfx/vmwgfx_ttm_glue.c
> @@ -33,10 +33,8 @@ int vmw_mmap(struct file *filp, struct vm_area_struct *vma)
> struct drm_file *file_priv;
> struct vmw_private *dev_priv;
>
> - if (unlikely(vma->vm_pgoff < VMWGFX_FILE_PAGE_OFFSET)) {
> - DRM_ERROR("Illegal attempt to mmap old fifo space.\n");
> + if (unlikely(vma->vm_pgoff < VMWGFX_FILE_PAGE_OFFSET))
> return -EINVAL;
> - }
>
> file_priv = filp->private_data;
> dev_priv = vmw_priv(file_priv->minor->dev);
next prev parent reply other threads:[~2017-09-12 17:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-12 17:35 Colin King
2017-09-12 17:42 ` Thomas Hellstrom [this message]
2017-09-12 17:47 ` Colin Ian King
2017-09-12 17:54 ` Emil Velikov
2017-09-20 18:33 ` Daniel Vetter
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=211c7afe-c778-cf39-760a-05bc3a62e5db@vmware.com \
--to=thellstrom@vmware.com \
--cc=airlied@linux.ie \
--cc=colin.king@canonical.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-graphics-maintainer@vmware.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syeh@vmware.com \
/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
Powered by JetHome