From: manojnayak2005@gmail.com (Manoj Nayak)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Acquiring MSI vector physical address from kernel driver
Date: Tue, 29 Mar 2016 16:12:15 +0530 [thread overview]
Message-ID: <CAOsfsFKE+gfr==+cojSb-UtDVGc8K1qi=sn32wARMW4h5Wy2sw@mail.gmail.com> (raw)
In the following code, msi lower address, higher address and data
is written to msi_desc corresponding to a msi vector.
http://lxr.free-electrons.com/source/drivers/pci/msi.c#L311
We can get the msi message from irq using irq_get_msi_desc().
http://lxr.free-electrons.com/source/drivers/pci/msi.c#L349
struct msi_desc *entry = irq_get_msi_desc(irq);
Regards
Manoj Nayak
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20160329/2d9bfba1/attachment.html
next reply other threads:[~2016-03-29 10:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-29 10:42 Manoj Nayak [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-01-25 19:50 Acquiring MSI vector physical address from kernel driver Ramon Fried
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='CAOsfsFKE+gfr==+cojSb-UtDVGc8K1qi=sn32wARMW4h5Wy2sw@mail.gmail.com' \
--to=manojnayak2005@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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).