All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Deucher <alexdeucher@gmail.com>
To: Paul Menzel <pmenzel@molgen.mpg.de>,
	"Kuehling, Felix" <Felix.Kuehling@amd.com>
Cc: Alex Deucher <alexander.deucher@amd.com>,
	amd-gfx list <amd-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/amdkfd: make CRAT table missing message informational only
Date: Mon, 21 Feb 2022 17:45:55 -0500	[thread overview]
Message-ID: <CADnq5_OewXLcg-xD2Dzet_4uCVKoFVzA6ZqXegnQK+aNu_-LgQ@mail.gmail.com> (raw)
In-Reply-To: <90dd45cd-9cf4-d79f-dc32-76169fe10ee7@molgen.mpg.de>

On Fri, Feb 18, 2022 at 11:25 PM Paul Menzel <pmenzel@molgen.mpg.de> wrote:
>
> Dear Alex,
>
>
> Thank you for the patch.
>
> Am 18.02.22 um 21:42 schrieb Alex Deucher:
> > The driver has a fallback, to make the message informational
>
> s/to/so/?

fixed up locally.

>
> > rather than a warning.
>
> Maybe extend it a little?

Done.

>
> Component Resource Association Table (CRAT) are only applicable on some
> AMD APUs. The message is perfectly expected. Even on AMD APUs we can now
> fall back to treating it like a dGPU when the CRAT table is missing.
>
> > Bug: https://gitlab.freedesktop.org/drm/amd/-/issues/1906
> > Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
> > ---
> >   drivers/gpu/drm/amd/amdkfd/kfd_crat.c | 2 +-
> >   1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/gpu/drm/amd/amdkfd/kfd_crat.c b/drivers/gpu/drm/amd/amdkfd/kfd_crat.c
> > index 24898238b024..1eaabd2cb41b 100644
> > --- a/drivers/gpu/drm/amd/amdkfd/kfd_crat.c
> > +++ b/drivers/gpu/drm/amd/amdkfd/kfd_crat.c
> > @@ -1569,7 +1569,7 @@ int kfd_create_crat_image_acpi(void **crat_image, size_t *size)
> >       /* Fetch the CRAT table from ACPI */
> >       status = acpi_get_table(CRAT_SIGNATURE, 0, &crat_table);
> >       if (status == AE_NOT_FOUND) {
> > -             pr_warn("CRAT table not found\n");
> > +             pr_info("CRAT table not found\n");
>
> Maybe make it even a debug message, or only print it, when a
> corresponding AMD APU is found like in `kfd_is_acpi_crat_invalid()`?
> Especially since Linux logs
>
>          amdgpu: Virtual CRAT table created for CPU
>
>      later on.
>

I think it's still valid so you know that no CRAT table was found on
the platform.  @Kuehling, Felix any opinion?

Alex

> >               return -ENODATA;
> >       } else if (ACPI_FAILURE(status)) {
> >               const char *err = acpi_format_exception(status);
>
>
> Kind regards,
>
> Paul

  reply	other threads:[~2022-02-21 22:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-18 20:42 [PATCH] drm/amdkfd: make CRAT table missing message informational only Alex Deucher
2022-02-18 21:53 ` Felix Kuehling
2022-02-19  4:16 ` Paul Menzel
2022-02-21 22:45   ` Alex Deucher [this message]
2022-02-22 16:04     ` Felix Kuehling

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=CADnq5_OewXLcg-xD2Dzet_4uCVKoFVzA6ZqXegnQK+aNu_-LgQ@mail.gmail.com \
    --to=alexdeucher@gmail.com \
    --cc=Felix.Kuehling@amd.com \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=pmenzel@molgen.mpg.de \
    /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.