search for: ioremap_

...shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid xsaveopt bugs : bogomips : 4789.40 clflush size : 64 cache_alignment : 64 address sizes : 39 bits physical, 48 bits virtual power management: kernel log: Feb 07 22:29:34 kernel: mmiotrace: ioremap_*(0xf6000000, 0x1000) = ffffc90000044000 Feb 07 22:29:34 kernel: mmiotrace: Unmapping ffffc90000044000. Feb 07 22:29:34 kernel: mmiotrace: ioremap_*(0xf6000000, 0x1000) = ffffc90000046000 Feb 07 22:29:34 kernel: mmiotrace: Unmapping ffffc90000046000. Feb 07 22:29:34 kernel: nvidia-nvlink: Nvlink Cor...

...the BAR. >> >> >> > Um wait, this memory is behind an already mapped bar? I think ioremap on >> > ARM defaults to uncached mappings, so if you want to access the memory >> > behind this bar as WC you need to map the BAR as a whole as WC by using >> > ioremap_wc. >> >> Tried mapping the BAR using ioremap_wc(), but to no avail. On the other >> hand, could it be that VRAM BOs end up creating a mapping over an >> already-mapped region? I seem to remember that ARM might not like it... > > Multiple mapping are generally allowed,...

...>>>>> Um wait, this memory is behind an already mapped bar? I think ioremap on >>>>> ARM defaults to uncached mappings, so if you want to access the memory >>>>> behind this bar as WC you need to map the BAR as a whole as WC by using >>>>> ioremap_wc. >>>> >>>> Tried mapping the BAR using ioremap_wc(), but to no avail. On the other >>>> hand, could it be that VRAM BOs end up creating a mapping over an >>>> already-mapped region? I seem to remember that ARM might not like it... >>> >&...

...gt;> > >> > Um wait, this memory is behind an already mapped bar? I think ioremap on > >> > ARM defaults to uncached mappings, so if you want to access the memory > >> > behind this bar as WC you need to map the BAR as a whole as WC by using > >> > ioremap_wc. > >> > >> Tried mapping the BAR using ioremap_wc(), but to no avail. On the other > >> hand, could it be that VRAM BOs end up creating a mapping over an > >> already-mapped region? I seem to remember that ARM might not like it... > > > > Multiple m...

...;> Um wait, this memory is behind an already mapped bar? I think ioremap on > >>>>> ARM defaults to uncached mappings, so if you want to access the memory > >>>>> behind this bar as WC you need to map the BAR as a whole as WC by using > >>>>> ioremap_wc. > >>>> > >>>> Tried mapping the BAR using ioremap_wc(), but to no avail. On the other > >>>> hand, could it be that VRAM BOs end up creating a mapping over an > >>>> already-mapped region? I seem to remember that ARM might not like it.....

...-mapped BO, e.g. a BO >> mapped through the BAR. >> > Um wait, this memory is behind an already mapped bar? I think ioremap on > ARM defaults to uncached mappings, so if you want to access the memory > behind this bar as WC you need to map the BAR as a whole as WC by using > ioremap_wc. Tried mapping the BAR using ioremap_wc(), but to no avail. On the other hand, could it be that VRAM BOs end up creating a mapping over an already-mapped region? I seem to remember that ARM might not like it...

...wait, this memory is behind an already mapped bar? I think ioremap on >>>>>>> ARM defaults to uncached mappings, so if you want to access the memory >>>>>>> behind this bar as WC you need to map the BAR as a whole as WC by using >>>>>>> ioremap_wc. >>>>>> >>>>>> Tried mapping the BAR using ioremap_wc(), but to no avail. On the other >>>>>> hand, could it be that VRAM BOs end up creating a mapping over an >>>>>> already-mapped region? I seem to remember that ARM might n...