Skip to content

rmapi: keep kernel clients' user BAR1 mappings in one range #1403

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
SammyTourani wants to merge 1 commit into
base: main
Choose a base branch
from
+11 −1
Open

rmapi: keep kernel clients' user BAR1 mappings in one range #1403

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 11 additions & 1 deletion src/nvidia/src/kernel/rmapi/mapping_cpu.c
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -484,7 +484,17 @@ memMap_IMPL
// Below, we only map one GPU's address for CPU access, so we can use UNICAST here
NvU32 busMapFbFlags = BUS_MAP_FB_FLAGS_MAP_UNICAST;
#if defined(NV_UNIX)
busMapFbFlags |= pMapParams->bKernel ? 0 : BUS_MAP_FB_FLAGS_ALLOW_DISCONTIG;
//
// A discontiguous mapping only works when every range of the
// memArea gets mapped, as the mmap path does for user clients.
// A kernel client's MEM_SPACE_USER mapping only returns the
// start address, and the caller maps the whole length from it.
//
if (!pMapParams->bKernel &&
(DRF_VAL(OS33, _FLAGS, _MEM_SPACE, pMapParams->flags) != NVOS33_FLAGS_MEM_SPACE_USER))
{
busMapFbFlags |= BUS_MAP_FB_FLAGS_ALLOW_DISCONTIG;
}
#endif
if(DRF_VAL(OS33, _FLAGS, _MAPPING, pMapParams->flags) == NVOS33_FLAGS_MAPPING_DIRECT)
{
Expand Down