search for: ranges

...ns = kvmalloc_array(ttm->num_pages, sizeof(*range->pfns), - GFP_KERNEL); - if (unlikely(!range->pfns)) { + range->hmm_pfns = kvmalloc_array(ttm->num_pages, + sizeof(*range->hmm_pfns), GFP_KERNEL); + if (unlikely(!range->hmm_pfns)) { r = -ENOMEM; goto out_free_ranges; } @@ -867,7 +853,7 @@ int amdgpu_ttm_tt_get_user_pages(struct amdgpu_bo *bo, struct page **pages) * the notifier_lock, and mmu_interval_read_retry() must be done first. */ for (i = 0; i < ttm->num_pages; i++) - pages[i] = hmm_device_entry_to_page(range, range->pfns[i]); + page...

Hi Jérôme, Ben, Felxi and Jason, below is a series against the hmm tree which cleans up various minor bits and allows HMM_MIRROR to be built on all architectures. Diffstat: 7 files changed, 81 insertions(+), 171 deletions(-) A git tree is also available at: git://git.infradead.org/users/hch/misc.git hmm-cleanups Gitweb:

...ns = kvmalloc_array(ttm->num_pages, sizeof(*range->pfns), - GFP_KERNEL); - if (unlikely(!range->pfns)) { + range->hmm_pfns = kvmalloc_array(ttm->num_pages, + sizeof(*range->hmm_pfns), GFP_KERNEL); + if (unlikely(!range->hmm_pfns)) { r = -ENOMEM; goto out_free_ranges; } @@ -867,7 +853,7 @@ int amdgpu_ttm_tt_get_user_pages(struct amdgpu_bo *bo, struct page **pages) * the notifier_lock, and mmu_interval_read_retry() must be done first. */ for (i = 0; i < ttm->num_pages; i++) - pages[i] = hmm_device_entry_to_page(range, range->pfns[i]); + page...

...dmirror_hmm_flags[HMM_PFN_FLAG_MAX] = { - [HMM_PFN_VALID] = DPT_VALID, - [HMM_PFN_WRITE] = DPT_WRITE, -}; - -static const uint64_t dmirror_hmm_values[HMM_PFN_VALUE_MAX] = { - [HMM_PFN_NONE] = 0, - [HMM_PFN_ERROR] = 0x10, - [HMM_PFN_SPECIAL] = 0x10, -}; - /* * Data structure to track address ranges and register for mmu interval * notifier updates. @@ -175,7 +160,7 @@ static inline struct dmirror_device *dmirror_page_to_device(struct page *page) static int dmirror_do_fault(struct dmirror *dmirror, struct hmm_range *range) { - uint64_t *pfns = range->pfns; + unsigned long *pfns = range...

...es, sizeof(*range->pfns), > - GFP_KERNEL); > - if (unlikely(!range->pfns)) { > + range->hmm_pfns = kvmalloc_array(ttm->num_pages, > + sizeof(*range->hmm_pfns), GFP_KERNEL); > + if (unlikely(!range->hmm_pfns)) { > r = -ENOMEM; > goto out_free_ranges; > } > @@ -867,7 +853,7 @@ int amdgpu_ttm_tt_get_user_pages(struct amdgpu_bo *bo, struct page **pages) > * the notifier_lock, and mmu_interval_read_retry() must be done first. > */ > for (i = 0; i < ttm->num_pages; i++) > - pages[i] = hmm_device_entry_to_page(rang...

...10dc788c..1225b3c87aba05 100644 --- a/include/linux/hmm.h +++ b/include/linux/hmm.h @@ -68,29 +68,6 @@ #include <linux/completion.h> #include <linux/mmu_notifier.h> - -/* - * struct hmm - HMM per mm struct - * - * @mm: mm struct this HMM struct is bound to - * @lock: lock protecting ranges list - * @ranges: list of range being snapshotted - * @mirrors: list of mirrors for this mm - * @mmu_notifier: mmu notifier to track updates to CPU page table - * @mirrors_sem: read/write semaphore protecting the mirrors list - * @wq: wait queue for user waiting on a range invalidation - * @notifie...

Hi Jérôme, Ben and Jason, below is a series against the hmm tree which fixes up the mmap_sem locking in nouveau and while at it also removes leftover legacy HMM APIs only used by nouveau.

...last time...hoping for some this time. :) Currently I'm only coming up with brute force solutions to this issue (loops). I'm wondering if anyone has a better way to do this. Thank you for your help in advance! The problem: I have endpoints of one x range (x_rng) and an unknown number of s ranges (s[#]_rng) also defined by the range endpoints. I'd like to remove the x ranges that overlap with the s ranges. The examples below demonstrate what I mean. What is the best way to do this? Ex 1. For: x_rng = c(-100,100) s1_rng = c(-25.5,30) s2_rng = c(0.77,10) s3_rng = c(25,35) s4_rng = c(70...

All users pass PAGE_SIZE here, and if we wanted to support single entries for huge pages we should really just add a HMM_FAULT_HUGEPAGE flag instead that uses the huge page size instead of having the caller calculate that size once, just for the hmm code to verify it. Signed-off-by: Christoph Hellwig <hch at lst.de> --- drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c | 1 -

All users pass PAGE_SIZE here, and if we wanted to support single entries for huge pages we should really just add a HMM_FAULT_HUGEPAGE flag instead that uses the huge page size instead of having the caller calculate that size once, just for the hmm code to verify it. Signed-off-by: Christoph Hellwig <hch at lst.de> Acked-by: Felix Kuehling <Felix.Kuehling at amd.com> ---

Hi Jérôme, Ben, Felix and Jason, below is a series against the hmm tree which cleans up various minor bits and allows HMM_MIRROR to be built on all architectures. Diffstat: 11 files changed, 94 insertions(+), 210 deletions(-) A git tree is also available at: git://git.infradead.org/users/hch/misc.git hmm-cleanups.2 Gitweb:

...; >>>>>> Thank you >>>>>> >>>>>> >>>>> >>>>> Do not change the lower range value on a Samba fileserver once >>>>> set, you can raise the upper value, but there is a proviso, the >>>>> ranges must not overlap. This means your lines above are invalid, >>>>> they both start at '5000' and the entire '*' range is inside the >>>>> 'SERVERAD' range. >>>>> >>>>> If you change the lower range and you are using...

The start, end and page_shift values are all saved in the range structure, so we might as well use that for argument passing. Signed-off-by: Christoph Hellwig <hch at lst.de> --- Documentation/vm/hmm.rst | 2 +- drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c | 7 +++++-- drivers/gpu/drm/nouveau/nouveau_svm.c | 5 ++--- include/linux/hmm.h | 6 +-----

...gt; crossing, even so I changed them (mentioned above) >>>> >>>> Thank you >>>> >>>> >>> >>> Do not change the lower range value on a Samba fileserver once set, >>> you can raise the upper value, but there is a proviso, the ranges >>> must not overlap. This means your lines above are invalid, they both >>> start at '5000' and the entire '*' range is inside the 'SERVERAD' range. >>> >>> If you change the lower range and you are using the 'rid' backend, &gt...

Hi Jérôme, Ben and Jason, below is a series against the hmm tree which fixes up the mmap_sem locking in nouveau and while at it also removes leftover legacy HMM APIs only used by nouveau. The first 4 patches are a bug fix for nouveau, which I suspect should go into this merge window even if the code is marked as staging, just to avoid people copying the breakage. Changes since v1: - don't

Hi, trying to build syslinux on Linux. Please help. bash-2.05b$ uname -a Linux bongo 2.4.32-ARXc3 COHERENT #4-ARX (Build 2660) Sun May 21 15:35:22 CEST 2006 i686 i686 i386 GNU/Linux bash-2.05b$ BUILD/syslinux-3.11/opt/nasm-0.98.38-2/bin/nasm -version NASM version 0.98.38 compiled on Jun 26 2006 But failed with: + make NASM=/home/axel/p/rpm/BUILD/syslinux-3.11/opt/nasm/bin /nasm

Here are seven more patches for things I found to clean up. This was based on top of Christoph's seven patches: "hmm_range_fault related fixes and legacy API removal v3". I assume this will go into Jason's tree since there will likely be more HMM changes in this cycle. Changes from v1 to v2: Added AMD GPU to hmm_update removal. Added 2 patches from Christoph. Added 2 patches as

Hi Jérôme, Ben and Jason, below is a series against the hmm tree which fixes up the mmap_sem locking in nouveau and while at it also removes leftover legacy HMM APIs only used by nouveau. Changes since v1: - don't return the valid state from hmm_range_unregister - additional nouveau cleanups

When I run a macro that uses RExcel, I get a dialog box that says "Microsoft Excel is waiting for another application to complete an OLE action." There is no error in the RExcel commands in the macro, of that I am sure. The box appears to be related to the inclusion of RunRFile commands. The macro will run through the second RunRFile command, but will not execute the

...if the User to the fact that the idmap values be >> crossing, even so I changed them (mentioned above) >> >> Thank you >> >> > > Do not change the lower range value on a Samba fileserver once set, > you can raise the upper value, but there is a proviso, the ranges must > not overlap. This means your lines above are invalid, they both start > at '5000' and the entire '*' range is inside the 'SERVERAD' range. > > If you change the lower range and you are using the 'rid' backend, all > your IDs will change. >...