From: Joerg Roedel <joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
To: Scott Wood <swood-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: "Luis Claudio R. Goncalves"
<lgoncalv-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
Clark Williams <williams-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
Myron Stowe <myron.stowe-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Subject: Re: [PATCH 2/2] amd/iommu: Use raw locks on atomic context paths
Date: Tue, 13 Feb 2018 14:18:53 +0100 [thread overview]
Message-ID: <20180213131853.qf2benuztfdihiew@8bytes.org> (raw)
In-Reply-To: <20180121092854.28290-2-swood-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
On Sun, Jan 21, 2018 at 03:28:54AM -0600, Scott Wood wrote:
> Several functions in this driver are called from atomic context,
> and thus raw locks must be used in order to be safe on PREEMPT_RT.
>
> This includes paths that must wait for command completion, which is
> a potential PREEMPT_RT latency concern but not easily avoidable.
>
> Signed-off-by: Scott Wood <swood-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
> ---
> drivers/iommu/amd_iommu.c | 30 +++++++++++++++---------------
> drivers/iommu/amd_iommu_init.c | 2 +-
> drivers/iommu/amd_iommu_types.h | 4 ++--
> 3 files changed, 18 insertions(+), 18 deletions(-)
Applied, thanks.
next prev parent reply other threads:[~2018-02-13 13:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-21 9:28 [PATCH 1/2] iommu/amd: Avoid get_irq_table() from atomic context Scott Wood
[not found] ` <20180121092854.28290-1-swood-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2018-01-21 9:28 ` [PATCH 2/2] amd/iommu: Use raw locks on atomic context paths Scott Wood
[not found] ` <20180121092854.28290-2-swood-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2018-02-13 13:18 ` Joerg Roedel [this message]
2018-02-13 13:13 ` [PATCH 1/2] iommu/amd: Avoid get_irq_table() from atomic context Joerg Roedel
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=20180213131853.qf2benuztfdihiew@8bytes.org \
--to=joro-zlv9swrftaidnm+yrofe0a@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=lgoncalv-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=myron.stowe-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=swood-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=williams-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.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;
as well as URLs for NNTP newsgroup(s).