From: "Zhang, Jerry" <Jerry.Zhang@amd.com>
To: "Michel Dänzer" <michel@daenzer.net>
Cc: "Koenig, Christian" <Christian.Koenig@amd.com>,
"Huang, Ray" <Ray.Huang@amd.com>,
"Zhang, Jerry" <Jerry.Zhang@amd.com>,
David Airlie <airlied@linux.ie>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] drm/ttm: Use drm_debug_printer for all ttm_bo_mem_space_debug output
Date: Fri, 21 Dec 2018 01:29:18 +0000 [thread overview]
Message-ID: <E6378BBE-6AB0-4B75-B59F-81315DB397E5@amd.com> (raw)
In-Reply-To: <20181220112209.8063-1-michel@daenzer.net>
> 在 2018年12月20日,19:22,Michel Dänzer <michel@daenzer.net> 写道:
>
> From: Michel Dänzer <michel.daenzer@amd.com>
Reviewed-by: Junwei Zhang <Jerry.Zhang@amd.com>
>
> No need for pr_err here, the pr_err message in ttm_bo_evict is enough
> to draw attention to something not going as planned.
>
> Signed-off-by: Michel Dänzer <michel.daenzer@amd.com>
> ---
>
> Similar to a previous patch, but this one leaves the pr_err messages in
> ttm_bo_evict untouched.
>
> drivers/gpu/drm/ttm/ttm_bo.c | 33 +++++++++++++++++----------------
> 1 file changed, 17 insertions(+), 16 deletions(-)
>
> diff --git a/drivers/gpu/drm/ttm/ttm_bo.c b/drivers/gpu/drm/ttm/ttm_bo.c
> index d87935bf8e30..0ec08394e17a 100644
> --- a/drivers/gpu/drm/ttm/ttm_bo.c
> +++ b/drivers/gpu/drm/ttm/ttm_bo.c
> @@ -77,38 +77,39 @@ static inline int ttm_mem_type_from_place(const struct ttm_place *place,
> return 0;
> }
>
> -static void ttm_mem_type_debug(struct ttm_bo_device *bdev, int mem_type)
> +static void ttm_mem_type_debug(struct ttm_bo_device *bdev, struct drm_printer *p,
> + int mem_type)
> {
> struct ttm_mem_type_manager *man = &bdev->man[mem_type];
> - struct drm_printer p = drm_debug_printer(TTM_PFX);
>
> - pr_err(" has_type: %d\n", man->has_type);
> - pr_err(" use_type: %d\n", man->use_type);
> - pr_err(" flags: 0x%08X\n", man->flags);
> - pr_err(" gpu_offset: 0x%08llX\n", man->gpu_offset);
> - pr_err(" size: %llu\n", man->size);
> - pr_err(" available_caching: 0x%08X\n", man->available_caching);
> - pr_err(" default_caching: 0x%08X\n", man->default_caching);
> + drm_printf(p, " has_type: %d\n", man->has_type);
> + drm_printf(p, " use_type: %d\n", man->use_type);
> + drm_printf(p, " flags: 0x%08X\n", man->flags);
> + drm_printf(p, " gpu_offset: 0x%08llX\n", man->gpu_offset);
> + drm_printf(p, " size: %llu\n", man->size);
> + drm_printf(p, " available_caching: 0x%08X\n", man->available_caching);
> + drm_printf(p, " default_caching: 0x%08X\n", man->default_caching);
> if (mem_type != TTM_PL_SYSTEM)
> - (*man->func->debug)(man, &p);
> + (*man->func->debug)(man, p);
> }
>
> static void ttm_bo_mem_space_debug(struct ttm_buffer_object *bo,
> struct ttm_placement *placement)
> {
> + struct drm_printer p = drm_debug_printer(TTM_PFX);
> int i, ret, mem_type;
>
> - pr_err("No space for %p (%lu pages, %luK, %luM)\n",
> - bo, bo->mem.num_pages, bo->mem.size >> 10,
> - bo->mem.size >> 20);
> + drm_printf(&p, "No space for %p (%lu pages, %luK, %luM)\n",
> + bo, bo->mem.num_pages, bo->mem.size >> 10,
> + bo->mem.size >> 20);
> for (i = 0; i < placement->num_placement; i++) {
> ret = ttm_mem_type_from_place(&placement->placement[i],
> &mem_type);
> if (ret)
> return;
> - pr_err(" placement[%d]=0x%08X (%d)\n",
> - i, placement->placement[i].flags, mem_type);
> - ttm_mem_type_debug(bo->bdev, mem_type);
> + drm_printf(&p, " placement[%d]=0x%08X (%d)\n",
> + i, placement->placement[i].flags, mem_type);
> + ttm_mem_type_debug(bo->bdev, &p, mem_type);
> }
> }
>
> --
> 2.20.1
>
prev parent reply other threads:[~2018-12-21 1:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-20 11:22 Michel Dänzer
2018-12-20 13:34 ` Christian König
2018-12-21 1:29 ` Zhang, Jerry [this message]
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=E6378BBE-6AB0-4B75-B59F-81315DB397E5@amd.com \
--to=jerry.zhang@amd.com \
--cc=Christian.Koenig@amd.com \
--cc=Ray.Huang@amd.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michel@daenzer.net \
/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®