From: Joerg Roedel <joro@8bytes.org>
To: Artem Savkov <asavkov@redhat.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
iommu@lists.linux-foundation.org, x86@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iommu/amd: Fix schedule-while-atomic BUG in initialization code
Date: Wed, 26 Jul 2017 15:41:35 +0200 [thread overview]
Message-ID: <20170726134135.GA21502@8bytes.org> (raw)
In-Reply-To: <20170726132505.cw4xmstcrbmuduyz@shodan.usersys.redhat.com>
On Wed, Jul 26, 2017 at 03:25:05PM +0200, Artem Savkov wrote:
> On Wed, Jul 26, 2017 at 02:26:14PM +0200, Joerg Roedel wrote:
> > Yes, that should fix it, but I think its better to just move the
> > register_syscore_ops() call to a later initialization step, like in the
> > patch below. I tested it an will queue it to my iommu/fixes branch.
>
> Checked it as well just in case, didn't see any issues. Thank you.
>
> Reported-and-tested-by: Artem Savkov <asavkov@redhat.com>
Thanks for testing it! I added your's and Thomas' tags and applied the
patch to my tree. It should go upstream this week.
Joerg
prev parent reply other threads:[~2017-07-26 13:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-25 13:56 amd-iommu/x2apic: sleeping function called from invalid context Artem Savkov
[not found] ` <20170725135618.hev4vj7w24gm3a5q-TUG+jSMfqtFQcClZ3XN9yxcY2uh10dtjAL8bYrjMMd8@public.gmane.org>
2017-07-26 10:42 ` Thomas Gleixner
2017-07-26 12:26 ` [PATCH] iommu/amd: Fix schedule-while-atomic BUG in initialization code Joerg Roedel
2017-07-26 13:23 ` Thomas Gleixner
2017-07-26 13:25 ` Artem Savkov
2017-07-26 13:41 ` Joerg Roedel [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=20170726134135.GA21502@8bytes.org \
--to=joro@8bytes.org \
--cc=asavkov@redhat.com \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).