All of lore.kernel.org
 help / color / mirror / Atom feed
From: Balasubramani Vivekanandan <balasubramani.vivekanandan@intel.com>
To: Matthew Auld <matthew.william.auld@gmail.com>
Cc: intel-xe@lists.freedesktop.org
Subject: Re: [Intel-xe] [PATCH 2/2] drm/xe: Change log level of error prints
Date: Tue, 25 Apr 2023 15:00:33 +0530	[thread overview]
Message-ID: <ZEeduZQnpvr6GcFC@bvivekan-mobl> (raw)
In-Reply-To: <CAM0jSHNhE_gv_ZwacK2qRtsgO1oY2oM1J+fU5bmgSK22Nr2=cQ@mail.gmail.com>

On 21.04.2023 17:43, Matthew Auld wrote:
> On Fri, 21 Apr 2023 at 16:39, Balasubramani Vivekanandan
> <balasubramani.vivekanandan@intel.com> wrote:
> >
> > Error prints are logged using drm_err log level.
> >
> > Signed-off-by: Balasubramani Vivekanandan <balasubramani.vivekanandan@intel.com>
> > ---
> >  drivers/gpu/drm/xe/xe_mmio.c | 6 +++---
> >  1 file changed, 3 insertions(+), 3 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/xe/xe_mmio.c b/drivers/gpu/drm/xe/xe_mmio.c
> > index 8bd39c3e65ae..7a0fcb37aab0 100644
> > --- a/drivers/gpu/drm/xe/xe_mmio.c
> > +++ b/drivers/gpu/drm/xe/xe_mmio.c
> > @@ -59,8 +59,8 @@ _resize_bar(struct xe_device *xe, int resno, resource_size_t size)
> >
> >         ret = pci_resize_resource(pdev, resno, bar_size);
> >         if (ret) {
> > -               drm_info(&xe->drm, "Failed to resize BAR%d to %dM (%pe)\n",
> > -                        resno, 1 << bar_size, ERR_PTR(ret));
> > +               drm_err(&xe->drm, "Failed to resize BAR%d to %dM (%pe)\n",
> > +                       resno, 1 << bar_size, ERR_PTR(ret));
> 
> Not sure if we should treat it as an error, also there might be
> nothing the user can really do. The driver should still be functional.
Yeah you are right, else it would create unnecessary failures in the CI.
> 
> >                 return -1;
> >         }
> >
> > @@ -119,7 +119,7 @@ static int xe_resize_vram_bar(struct xe_device *xe, resource_size_t vram_size)
> >         }
> >
> >         if (!root_res) {
> > -               drm_info(&xe->drm, "Can't resize VRAM BAR - platform support is missing. Consider enabling 'Resizable BAR' support in your BIOS\n");
> > +               drm_err(&xe->drm, "Can't resize VRAM BAR - platform support is missing. Consider enabling 'Resizable BAR' support in your BIOS\n");
> 
> Same here.
Also here.

I will drop this patch in the next version.

Regards,
Bala
> 
> >                 return -1;
> >         }
> >
> > --
> > 2.34.1
> >

  reply	other threads:[~2023-04-25  9:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-21 15:38 [Intel-xe] [PATCH 1/2] drm/xe: Keep all resize bar related prints inside xe_resize_vram_bar Balasubramani Vivekanandan
2023-04-21 15:38 ` [Intel-xe] [PATCH 2/2] drm/xe: Change log level of error prints Balasubramani Vivekanandan
2023-04-21 16:43   ` Matthew Auld
2023-04-25  9:30     ` Balasubramani Vivekanandan [this message]
2023-04-21 15:41 ` [Intel-xe] ✓ CI.Patch_applied: success for series starting with [1/2] drm/xe: Keep all resize bar related prints inside xe_resize_vram_bar Patchwork
2023-04-21 15:42 ` [Intel-xe] ✓ CI.KUnit: " Patchwork
2023-04-21 15:46 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-04-21 16:09 ` [Intel-xe] ○ CI.BAT: info " Patchwork
2023-04-21 16:31 ` [Intel-xe] [PATCH 1/2] " Matthew Auld
2023-04-25  9:28   ` Balasubramani Vivekanandan
2023-04-25 10:25     ` Matthew Auld
2023-04-25 10:42       ` Balasubramani Vivekanandan
2023-04-25 10:46         ` Matthew Auld

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=ZEeduZQnpvr6GcFC@bvivekan-mobl \
    --to=balasubramani.vivekanandan@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=matthew.william.auld@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.