From: Niket Kandya <niketkandya@google.com>
To: dev@dpdk.org
Cc: Tanjore Suresh <tansuresh@google.com>
Subject: Question about VFIO_DEVICE_RESET
Date: Fri, 30 Sep 2022 13:48:05 -0700 [thread overview]
Message-ID: <CACmnOiHkoGGVu4OwuG2N_66NJ_W=2LMV4pSz-RCRNDBW8UOx1A@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 661 bytes --]
Hi Folks,
After running into a reset related issue recently and browsing through
code, I reached at this function *pci_rte_vfio_setup_device*.
I do not understand the rationale of the *VFIO_DEVICE_RESET* at the end of
this function.
Looks like the function sets up interrupts, enables bus mastering and then
resets the device?
See below from the PCIe spec:
*`Note that the controls that enable the Function to initiate requests on
PCI Express are cleared, including Bus Master Enable, MSI Enable, and the
like, effectively causing the Function to become quiescent on the Link.`*
Is the function effectively undoing everything by doing the reset at the
end?
[-- Attachment #2: Type: text/html, Size: 786 bytes --]
reply other threads:[~2022-10-03 6:41 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='CACmnOiHkoGGVu4OwuG2N_66NJ_W=2LMV4pSz-RCRNDBW8UOx1A@mail.gmail.com' \
--to=niketkandya@google.com \
--cc=dev@dpdk.org \
--cc=tansuresh@google.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;
as well as URLs for NNTP newsgroup(s).