search for: unmapped

...am using the testing version of NUT from SVN at changeset 582. I have successfully created a stub for newhidups driver for my Dynex DX-800U UPS, but I am completely lost on the customization of it. I've followed the hid-subdrivers.txt instructions and I understand I need to map all the "unmapped.*" lines of my dynex-hid.c to NUT functions. However, I can't make heads or tails of what I'm supposed to change. Can someone take some time to help a struggling noob? Here's some info I hope helps: # /usr/src/nut-testing# pico /usr/local/ups/etc/ups.conf [mythbox]...

...VRAM, and has size 0x8000 or 32kB. My hardware is NV20 (gf3). DRM and DDX from git around 9th March. I found this while mmiotracing nouveau. I start the trace, load drm.ko and nouveau.ko, start X three times in a row, unload nouveau.ko and drm.ko. Now when I stop mmiotracing, it reports three non-unmapped io-mappings as described above. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

This is version 0.5 of the virtio-iommu specification, the paravirtualized IOMMU. This version addresses feedback from v0.4 and adds an event virtqueue. Please find the specification, LaTeX sources and pdf, at: git://linux-arm.org/virtio-iommu.git viommu/v0.5 http://linux-arm.org/git?p=virtio-iommu.git;a=blob;f=dist/v0.5/virtio-iommu-v0.5.pdf A detailed changelog since v0.4 follows. You can find

This is version 0.5 of the virtio-iommu specification, the paravirtualized IOMMU. This version addresses feedback from v0.4 and adds an event virtqueue. Please find the specification, LaTeX sources and pdf, at: git://linux-arm.org/virtio-iommu.git viommu/v0.5 http://linux-arm.org/git?p=virtio-iommu.git;a=blob;f=dist/v0.5/virtio-iommu-v0.5.pdf A detailed changelog since v0.4 follows. You can find

Hi, Xenoprof buffers are mapped into the kernel using direct_kernel_remap_pfn_range(). I need to unmap the buffer when it is not needed anymore. However, I could not find any function that unmaps pages previously mapped with direct_kernel_remap_pfn_range(). Any suggestion on how to do this? Thanks Renato _______________________________________________ Xen-devel mailing list

On Fri, Oct 12, 2018 at 02:06:28PM -0700, Daniel Verkamp wrote: > From: Changpeng Liu <changpeng.liu at intel.com> > > In commit 88c85538, "virtio-blk: add discard and write zeroes features > to specification" (https://github.com/oasis-tcs/virtio-spec), the virtio There is some issues in this spec. For one using the multiple ranges also for write zeroes is rather

On Fri, Oct 12, 2018 at 02:06:28PM -0700, Daniel Verkamp wrote: > From: Changpeng Liu <changpeng.liu at intel.com> > > In commit 88c85538, "virtio-blk: add discard and write zeroes features > to specification" (https://github.com/oasis-tcs/virtio-spec), the virtio There is some issues in this spec. For one using the multiple ranges also for write zeroes is rather

Hello, I find "discard":"unmap" is defaultly enabled in qemu cmdline(libvirt v6.6, qemu v5.1): XML: <disk type="file" device="disk"> <driver name="qemu" type="qcow2"/> <source file="/var/lib/libvirt/images/new.qcow2" index="2"/> <backingStore/> <target

...> /* --------------------------------------------------------------- */ > /* HID2NUT lookup table */ > /* --------------------------------------------------------------- */ > > static hid_info_t jundatech_hid2nut[] = { > > { "unmapped.ups.powersummary.capacitymode", 0, 0, > "UPS.PowerSummary.CapacityMode", NULL, "%.0f", 0, NULL }, > { "unmapped.ups.powersummary.designcapacity", 0, 0, > "UPS.PowerSummary.DesignCapacity", NULL, "%.0f", 0, NULL }, > { "unma...

On Thu, Apr 16, 2015 at 8:06 PM, Vince Hsu <vinceh at nvidia.com> wrote: > This patch implements a way to aggregate the small pages and make them be > mapped as big page(s) by utilizing the platform IOMMU if supported. And then > we can enable compression support for these big pages later. > > Signed-off-by: Vince Hsu <vinceh at nvidia.com> > --- >

...bal, and uses in the GPU caches. When a buffer is > mapped multiple times to different graphics contexts, we want to avoid cache > aliasing by mapping the buffer only once to IOMMU. We also want to unmap the > buffer from IOMMU only once after all the instances of the buffer have been > unmapped, or only when the buffer is actually freed to cache IOMMU mappings. > > Doing IOMMU mapping for the whole buffer with dma_map_sg is also faster than > mapping page by page, because you can do only one TLB invalidate in the end > of the loop instead of after every page if you use dma_map...

...ns to let the &drm_gpuva_manager + * calculate a sequence of operations to satisfy a given map or unmap request. + * + * Therefore the DRM GPU VA manager provides an algorithm implementing splitting + * and merging of existent GPU VA mappings with the ones that are requested to + * be mapped or unmapped. This feature is required by the Vulkan API to + * implement Vulkan 'Sparse Memory Bindings' - drivers UAPIs often refer to this + * as VM BIND. + * + * Drivers can call drm_gpuva_sm_map() to receive a sequence of callbacks + * containing map, unmap and remap operations for a given newly re...

On Thu, Oct 22, 2020 at 10:57:05 +0800, Han Han wrote: > Hello, > I find "discard":"unmap" is defaultly enabled in qemu cmdline(libvirt > v6.6, qemu v5.1): > XML: > <disk type="file" device="disk"> > <driver name="qemu" type="qcow2"/> > <source

...ns to let the &drm_gpuva_manager + * calculate a sequence of operations to satisfy a given map or unmap request. + * + * Therefore the DRM GPU VA manager provides an algorithm implementing splitting + * and merging of existent GPU VA mappings with the ones that are requested to + * be mapped or unmapped. This feature is required by the Vulkan API to + * implement Vulkan 'Sparse Memory Bindings' - drivers UAPIs often refer to this + * as VM BIND. + * + * Drivers can call drm_gpuva_sm_map() to receive a sequence of callbacks + * containing map, unmap and remap operations for a given newly re...

Hi Xen folks! I''ve faced with one strange thing in ARM version of Xen: when I use xc_map_foreign_bulk() to map some memory from domU to dom0, after unmap() for previous returned address - memory is not freed at all. Let''s look at call stack: xc_map_foreign() -> linux_privcmd_map_foreign_bulk() -> { addr = mmap(fd); ioctl(fd, IOCTL_PRIVCMD_MMAPBATCH_V2 );

...ns to let the &drm_gpuva_manager + * calculate a sequence of operations to satisfy a given map or unmap request. + * + * Therefore the DRM GPU VA manager provides an algorithm implementing splitting + * and merging of existent GPU VA mappings with the ones that are requested to + * be mapped or unmapped. This feature is required by the Vulkan API to + * implement Vulkan 'Sparse Memory Bindings' - drivers UAPIs often refer to this + * as VM BIND. + * + * Drivers can call drm_gpuva_sm_map() to receive a sequence of callbacks + * containing map, unmap and remap operations for a given newly re...

----- Forwarded message from braindevices <notifications@github.com> ----- Subject: [libguestfs/libguestfs] is there a way to set discard=unmap when using guestmount? (#52) I cannot find anything in the document. This option is very important for dynamic qcow2 disks. Without out this the IO is super slow even on tmpfs only 3MB/s. Subject: Re: [libguestfs/libguestfs] is there a way to

Is it possible to make discard='unmap' the default for virtio-scsi disks? (Related, is it possible to make virtio-scsi the default disk type, rather than virtio-blk?) Thanks! -- ======================================================================== Ian Pilcher arequipeno@gmail.com -------- "I grew up before Mark Zuckerberg invented

...ush in the dma-iommu path. Allow the iommu_unmap_fast to return newly freed page table pages and pass the freelist to queue_iova in the dma-iommu ops path. This patch is useful for iommu drivers (in this case the intel iommu driver) which need to wait for the ioTLB to be flushed before newly free/unmapped page table pages can be freed. This way we can still batch ioTLB free operations and handle the freelists. Change-log: V2: -fix missing parameter in mtk_iommu_v1.c Signed-off-by: Tom Murphy <murphyt7 at tcd.ie> --- drivers/iommu/amd/iommu.c | 14 ++++++++- drivers/iommu/arm-smmu-v3.c...

...ush in the dma-iommu path. Allow the iommu_unmap_fast to return newly freed page table pages and pass the freelist to queue_iova in the dma-iommu ops path. This patch is useful for iommu drivers (in this case the intel iommu driver) which need to wait for the ioTLB to be flushed before newly free/unmapped page table pages can be freed. This way we can still batch ioTLB free operations and handle the freelists. Change-log: V2: -fix missing parameter in mtk_iommu_v1.c Signed-off-by: Tom Murphy <murphyt7 at tcd.ie> --- drivers/iommu/amd/iommu.c | 14 ++++++++- drivers/iommu/arm-smmu-v3.c...