search for: release_area

...u_map(priv->domain, offset, page_to_phys(p), + PAGE_SIZE, IOMMU_READ | IOMMU_WRITE); + if (ret < 0) { + nv_error(priv, "IOMMU mapping failure: %d\n", ret); + + while (i-- > 0) { + offset -= PAGE_SIZE; + iommu_unmap(priv->domain, offset, PAGE_SIZE); + } + goto release_area; + } + } + + /* Bit 34 tells that an address is to be resolved through the IOMMU */ + r->offset |= BIT(34 - priv->iommu_pgshift); + + node->base._mem.offset = ((u64)r->offset) << priv->iommu_pgshift; + + INIT_LIST_HEAD(&node->base._mem.regions); + list_add_tail(&r-&...

...EAD | IOMMU_WRITE); if (ret < 0) { nvkm_error(subdev, "IOMMU mapping failure: %d\n", ret); while (i-- > 0) { offset -= PAGE_SIZE; - iommu_unmap(imem->domain, offset, PAGE_SIZE); + iommu_unmap_sync(imem->domain, offset, + PAGE_SIZE); } goto release_area; } -- 2.7.4

...delete /src /dest I invoked rsync as a root user. The source and destination filesystems (both reside on the NFS disks), have been exported with root privileges. 1) This file below does exists, however rsync complained of a "No such file or directory" error: readlink .snapshot/hourly.5/release_area/westport/westport_BRLS05/pci_unit/celtic/r undir2/pci_unit_celtic_minTTTT_noise_html/waveform73.html: No such file or directory 2) The file below does not exists on neither the source or destination side, but produced the error "No such file or directory" when attempting to transfer it....

...;-subset(AreaTidal.df, Year=="2003") ##Counts per Model and RA update_stat_defaults("bin",aes(y=..density..)) qplot(Depth, data = AreaTidal2003, binwidth = 10, origin=0,xlim=c(0,150), ylab="Larval Ratio")+ scale_x_continuous(breaks = breaks, labels=breaks)+facet_grid(Release_Area~Model) I would be hugely grateful for your help! Melanie ____________________________________________ Melanie Z?lck (Zoelck) PhD Candidate Galway-Mayo Institute of Technology Marine and Freshwater Research Centre Commercial Fisheries Research Group Department of Life Science Dublin Road Galway R...

Changes since v3: - Use a single dma_attr for all DMA-API allocations in instmem instead of one per allocation - Use device.info.ram_size instead of pfb->ram to check whether VRAM is present outside of nvkm Changes since v2: - Cleaner changes for ltc - Fixed typos in gk20a instmem IOMMU comments Changes since v1: - Add missing else condition in ltc - Remove extra flags that slipped into

Changes since v1: - Add missing else condition in ltc - Remove extra flags that slipped into nouveau_display.c and nv84_fence.c. Original cover letter: Patches 1-3 make the presence of a RAM device optional, and remove GK20A's dummy RAM driver we were using so far. On chips using shared memory, such a device can confuse the driver into moving objects where there is no need to, and can trick

A series I have waited too long to submit, and the recent refactoring made me pay the price of my perfectionism, so here are the features that are at least completed Patches 1-3 make the presence of a RAM device optional, and remove GK20A's dummy RAM driver we were using so far. On chips using shared memory, such a device can confuse the driver into moving objects where there is no need to,

Thanks Ilia for the v2 review! Here is the v3 of this IOMMU support for GK20A series. Changes since v2: - Cleaner changes for ltc - Fixed typos in gk20a instmem IOMMU comments Changes since v1: - Add missing else condition in ltc - Remove extra flags that slipped into nouveau_display.c and nv84_fence.c. Original cover letter: Patches 1-3 make the presence of a RAM device optional, and remove