From: Lennert Buytenhek <buytenh@wantstofly.org>
To: Joerg Roedel <joro@8bytes.org>
Cc: iommu@lists.linux-foundation.org
Subject: Re: [PATCH,RFC] iommu/amd: Use report_iommu_fault()
Date: Mon, 26 Jul 2021 19:26:12 +0300 [thread overview]
Message-ID: <YP7iJC9Dnvh5Wi+f@wantstofly.org> (raw)
In-Reply-To: <YP6iiR8wuszflhnN@8bytes.org>
On Mon, Jul 26, 2021 at 01:54:49PM +0200, Joerg Roedel wrote:
> Hi Lennert,
Hi Joerg,
> On Mon, Jul 19, 2021 at 12:54:43PM +0300, Lennert Buytenhek wrote:
> > + if (dev_data) {
> > + int report_flags;
> > +
> > + /*
> > + * AMD I/O Virtualization Technology (IOMMU) Specification,
> > + * revision 3.00, section 2.5.3 ("IO_PAGE_FAULT Event") says
> > + * that the RW ("read-write") bit is only valid if the I/O
> > + * page fault was caused by a memory transaction request
> > + * referencing a page that was marked present.
> > + */
> > + report_flags = 0;
> > + if ((flags & (EVENT_FLAG_TR | EVENT_FLAG_PR | EVENT_FLAG_I)) ==
> > + EVENT_FLAG_PR) {
> > + if (flags & EVENT_FLAG_RW)
> > + report_flags |= IOMMU_FAULT_WRITE;
> > + else
> > + report_flags |= IOMMU_FAULT_READ;
> > + }
> > +
> > + if (!report_iommu_fault(&dev_data->domain->domain,
> > + &pdev->dev, address, report_flags))
> > + goto out;
> > + }
>
> I'd like to limit calling report_iommu_fault() to dma-faults and leave
> IRQ remapping faults unreported. The IOMMU layer does not really care a
> lot about IRQs and a potential domain handler will also not be prepared
> to handler IRQ specific faults (there is no generic way to detect them).
I'm sorry -- this appears to have been a stupid oversight on my
part. New patch coming up.
Thanks,
Lennert
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
prev parent reply other threads:[~2021-07-26 16:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-19 9:54 [PATCH,RFC] iommu/amd: Use report_iommu_fault() Lennert Buytenhek
2021-07-22 19:26 ` Suthikulpanit, Suravee via iommu
2021-07-22 21:59 ` Lennert Buytenhek
2021-07-26 11:54 ` Joerg Roedel
2021-07-26 16:26 ` Lennert Buytenhek [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=YP7iJC9Dnvh5Wi+f@wantstofly.org \
--to=buytenh@wantstofly.org \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.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