Linux IOMMU Development
 help / color / mirror / Atom feed
From: Vasant Hegde <vasant.hegde@amd.com>
To: Jerry Snitselaar <jsnitsel@redhat.com>
Cc: iommu@lists.linux.dev, joro@8bytes.org,
	suravee.suthikulpanit@amd.com, joao.m.martins@oracle.com
Subject: Re: [PATCH 2/2] iommu/amd: Handle PPR log overflow
Date: Wed, 14 Jun 2023 12:58:54 +0530	[thread overview]
Message-ID: <da50028a-e935-98d3-a6f8-31e7a6a55216@amd.com> (raw)
In-Reply-To: <6rz75f6nq3ia2bymqjv5alxauqqdk5ea3emfew7nkdjvxtv5ks@qwyzsbg3ckxr>

Hi Jerry,

On 6/14/2023 1:59 AM, Jerry Snitselaar wrote:
> On Fri, Jun 09, 2023 at 10:17:46AM +0000, Vasant Hegde wrote:
>> Some ATS-capable peripherals can issue requests to the processor to service
>> peripheral page requests using PCIe PRI (the Page Request Interface). IOMMU
>> supports PRI using PPR log buffer. IOMMU writes PRI request to PPR log
>> buffer and sends PPR interrupt to host. When there is no space in the
>> PPR log buffer (PPR log overflow) it will set PprOverflow bit in 'MMIO
>> Offset 2020h IOMMU Status Register'. When this happens PPR log needs to be
>> restarted as specified in IOMMU spec [1] section 2.6.2.
>>
>> When handling the event it just resumes the PPR log without resizing
>> (similar to the way event and GA log overflow is handled).
>>
>> Failing to handle PPR overflow means device may not work properly as
>> IOMMU stops processing new PPR events from device.
>>
>> [1] https://www.amd.com/system/files/TechDocs/48882_3.07_PUB.pdf
>>
>> Signed-off-by: Vasant Hegde <vasant.hegde@amd.com>
> 
> Reviewed-by: Jerry Snitselaar <jsnitsel@redhat.com>

Thanks for the review.

> 
> Will the code re-org you are doing move the event log overflow check
> next to the event log processing check, like is done with the ga log
> and ppr log?

Yes. Its handled as part of IOMMU interrupt split series.

-Vasant


  reply	other threads:[~2023-06-14  7:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-09 10:17 [PATCH 0/2] iommu/amd: Add PPR overflow support Vasant Hegde
2023-06-09 10:17 ` [PATCH 1/2] iommu/amd: Generalize log overflow handling Vasant Hegde
2023-06-13 20:22   ` Jerry Snitselaar
2023-06-20 14:51   ` Joao Martins
2023-06-20 16:01     ` Vasant Hegde
2023-06-09 10:17 ` [PATCH 2/2] iommu/amd: Handle PPR log overflow Vasant Hegde
2023-06-13 20:29   ` Jerry Snitselaar
2023-06-14  7:28     ` Vasant Hegde [this message]
2023-06-20 14:53   ` Joao Martins

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=da50028a-e935-98d3-a6f8-31e7a6a55216@amd.com \
    --to=vasant.hegde@amd.com \
    --cc=iommu@lists.linux.dev \
    --cc=joao.m.martins@oracle.com \
    --cc=joro@8bytes.org \
    --cc=jsnitsel@redhat.com \
    --cc=suravee.suthikulpanit@amd.com \
    /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