From: "Jörg-Volker Peetz" <jvpeetz@web.de>
To: JoergRoedel <joro@8bytes.org>
Cc: SuraveeSuthikulpanit <suravee.suthikulpanit@amd.com>,
vasant.hegde@amd.com, WillDeacon <will@kernel.org>,
stable@vger.kernel.org
Subject: Re: Linux 5.17.5
Date: Mon, 2 May 2022 12:40:14 +0200 [thread overview]
Message-ID: <55b4e020-4b8d-382d-e45c-64ab00c082a1@web.de> (raw)
In-Reply-To: <Ym+oOjFrkdju5H6X@8bytes.org>
JoergRoedel wrote on 02/05/2022 11:45:
> [now with Vasants correct email address]
>
> Hi Jörg,
>
> can you please try the attached patch? It should get rid of the WARNING
> on your system.
>
> Suravee, Vasant, can you please test review the patch and report whether
> the GA log functionality is still working?
>
> Thanks,
>
> Joerg
>
Thanks for the patch.
Will test it today.
Regards,
Jörg.
> From 4fee768d5c23715eae31fed3b41cdf045e099aef Mon Sep 17 00:00:00 2001
> From: Joerg Roedel <jroedel@suse.de>
> Date: Mon, 2 May 2022 11:37:43 +0200
> Subject: [PATCH] iommu/amd: Do not poll GA_LOG_RUNNING mask at boot
>
> On some hardware it takes more than a second for the hardware to get
> the GA log into running state. This is too long to poll for in the AMD
> IOMMU driver code.
>
> Instead, check whehter initialization was successful before polling
> the log for the first time.
>
> Signed-off-by: Joerg Roedel <jroedel@suse.de>
> ---
> drivers/iommu/amd/amd_iommu_types.h | 3 +++
> drivers/iommu/amd/init.c | 13 ++-----------
> drivers/iommu/amd/iommu.c | 25 ++++++++++++++++++++++++-
> 3 files changed, 29 insertions(+), 12 deletions(-)
<snip>
next prev parent reply other threads:[~2022-05-02 10:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 13:11 Linux 5.17.5 Greg Kroah-Hartman
2022-04-27 13:11 ` Greg Kroah-Hartman
2022-05-01 12:37 ` Jörg-Volker Peetz
2022-05-01 14:23 ` Greg KH
2022-05-02 9:23 ` JoergRoedel
2022-05-02 9:42 ` JoergRoedel
2022-05-02 9:45 ` JoergRoedel
2022-05-02 10:40 ` Jörg-Volker Peetz [this message]
2022-05-02 22:17 ` Jörg-Volker Peetz
2022-05-04 8:16 ` JoergRoedel
2022-05-04 9:51 ` Jörg-Volker Peetz
2022-05-04 13:21 ` Jörg-Volker Peetz
2022-05-20 10:30 ` Joerg Roedel
2022-05-20 10:48 ` Jörg-Volker Peetz
2022-05-20 11:14 ` Joerg Roedel
2022-05-20 16:21 ` Jörg-Volker Peetz
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=55b4e020-4b8d-382d-e45c-64ab00c082a1@web.de \
--to=jvpeetz@web.de \
--cc=joro@8bytes.org \
--cc=stable@vger.kernel.org \
--cc=suravee.suthikulpanit@amd.com \
--cc=vasant.hegde@amd.com \
--cc=will@kernel.org \
/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