From: Joerg Roedel <joro@8bytes.org>
To: Mario Limonciello <mario.limonciello@amd.com>
Cc: suravee.suthikulpanit@amd.com, Vasant.Hegde@amd.com,
will@kernel.org, robin.murphy@arm.com, iommu@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iommu/amd: Mark interrupt as managed
Date: Fri, 9 Feb 2024 16:56:26 +0100 [thread overview]
Message-ID: <ZcZLKtFrbLax9lYP@8bytes.org> (raw)
In-Reply-To: <23361410-3b56-42fb-aea8-3be53bfe5ae1@amd.com>
On Fri, Feb 09, 2024 at 09:48:57AM -0600, Mario Limonciello wrote:
> Thanks! This problem should go all the way to when MSI support was
> introduced (2.6.28):
>
> a80dc3e0e0dc ("AMD IOMMU: add MSI interrupt support")
That makes most sense to me, also if it only uncovers with ...
>
> But I don't think that's a correct fixes tag because
> irq_managed wasn't introduced until 3.19:
>
> cffe0a2b5a34 ("x86, irq: Keep balance of IOAPIC pin reference count")
This one.
> But then I tried to go off the original introduction of the error message,
> but that's quite ancient.
>
> 1da177e4c3f4 ("Linux-2.6.12-rc2")
That is not relevant, as the first AMD IOMMU driver was only merged for
2.6.27 :)
> Cc: stable@vger.kernel.org # 3.19+
That makes sense too.
Regards,
Joerg
next prev parent reply other threads:[~2024-02-09 15:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-22 23:34 [PATCH] iommu/amd: Mark interrupt as managed Mario Limonciello
2024-02-05 16:31 ` Mario Limonciello
2024-02-09 8:24 ` Joerg Roedel
2024-02-09 15:48 ` Mario Limonciello
2024-02-09 15:56 ` Joerg Roedel [this message]
2024-02-12 11:24 ` Vasant Hegde
2024-02-16 14:17 ` 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=ZcZLKtFrbLax9lYP@8bytes.org \
--to=joro@8bytes.org \
--cc=Vasant.Hegde@amd.com \
--cc=iommu@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=robin.murphy@arm.com \
--cc=suravee.suthikulpanit@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