From: Sadanand Warrier <sadanandwarrier@gmail.com>
To: kernelnewbies@kernelnewbies.org
Subject: Controlling IOVA addresses generated by IOMMU
Date: Wed, 7 Apr 2021 16:56:30 -0400 [thread overview]
Message-ID: <CADJuq2w7_7rfNXjxDJUavrXAxWXi3aqna6dAHCCpqQgCrN5Kfg@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 354 bytes --]
Folks
Is there any kernel API or control mechanism for an IO-MMU that one
could use to specify that a buffer earmarked for DMA would always have an
IOVA greater than 4GB?
Basically if I used pci_map_sg and passed a scatter list I would like the
dma_address field in the scatterlist structure to be always greater than
4GB when it returned.
Thanks
S
[-- Attachment #1.2: Type: text/html, Size: 461 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
reply other threads:[~2021-04-07 20:56 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=CADJuq2w7_7rfNXjxDJUavrXAxWXi3aqna6dAHCCpqQgCrN5Kfg@mail.gmail.com \
--to=sadanandwarrier@gmail.com \
--cc=kernelnewbies@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).