From: poza@codeaurora.org
To: linux-pci@vger.kernel.org
Subject: PCIe Page request Interface Query (PRI)
Date: Tue, 21 Aug 2018 11:07:15 +0530 [thread overview]
Message-ID: <dbc3e13525d36553dfab3219fc6d4d81@codeaurora.org> (raw)
Hi All,
We have implemented the access control (ACS) for PRI request. If the BDF
number of the PRI request is outside of the control window, the request
will be dropped.
However, there is an requirement from PCIE spec 10.4, which says
Spec: 10.4 Page Request Services
A Page Request Message is a PCIe Message Request that is Routed to the
Root Complex (see the PCI Express Base Specification) with a Message
Code of 4 (0000 0100b). The mechanism employed at the RC to buffer
requests is implementation specific. The only requirement is that an RC
not silently discard requests.
My question on "The only requirement is that an RC not silently discard
requests."
1) what is SW’s expectation in this case? Is hw expected to trigger an
interrupt ?
2) any information to be logged anywhere into status register ?
3) What if there are back-to-back violations?
Regards,
Oza.
reply other threads:[~2018-08-21 8:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=dbc3e13525d36553dfab3219fc6d4d81@codeaurora.org \
--to=poza@codeaurora.org \
--cc=linux-pci@vger.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).