search for: range

From: Jason Gunthorpe <jgg at mellanox.com> Presumably the intent here was that hmm_range_fault() could put the data into some HW specific format and thus avoid some work. However, nothing actually does that, and it isn't clear how anything actually could do that as hmm_range_fault() provides CPU addresses which must be DMA mapped. Perhaps there is some special HW that does not nee...

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:

From: Jason Gunthorpe <jgg at mellanox.com> Presumably the intent here was that hmm_range_fault() could put the data into some HW specific format and thus avoid some work. However, nothing actually does that, and it isn't clear how anything actually could do that as hmm_range_fault() provides CPU addresses which must be DMA mapped. Perhaps there is some special HW that does not nee...

From: Jason Gunthorpe <jgg at mellanox.com> The API is a bit complicated for the uses we actually have, and disucssions for simplifying have come up a number of times. This small series removes the customizable pfn format and simplifies the return code of hmm_range_fault() All the drivers are adjusted to process in the simplified format. I would appreciated tested-by's for the two drivers, thanks! This passes the hmm tester with the following diff: diff --git a/lib/test_hmm.c b/lib/test_hmm.c index d75e18f2ffd245..a2442efa038c41 100644 --- a/lib/test_h...

[+Philip Yang] Am 2020-04-21 um 8:21 p.m. schrieb Jason Gunthorpe: > From: Jason Gunthorpe <jgg at mellanox.com> > > Presumably the intent here was that hmm_range_fault() could put the data > into some HW specific format and thus avoid some work. However, nothing > actually does that, and it isn't clear how anything actually could do that > as hmm_range_fault() provides CPU addresses which must be DMA mapped. > > Perhaps there is some spec...

...cumentation/vm/hmm.rst b/Documentation/vm/hmm.rst index 0a5960beccf76d..893a8ba0e9fefb 100644 --- a/Documentation/vm/hmm.rst +++ b/Documentation/vm/hmm.rst @@ -147,49 +147,16 @@ Address space mirroring implementation and API Address space mirroring's main objective is to allow duplication of a range of CPU page table into a device page table; HMM helps keep both synchronized. A device driver that wants to mirror a process address space must start with the -registration of an hmm_mirror struct:: - - int hmm_mirror_register(struct hmm_mirror *mirror, - struct mm_struct...

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.

...all edits). I didn't get any replies 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 =...

.../amdgpu/amdgpu_ttm.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c index 71d6e7087b0b..8bf79288c4e2 100644 --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c @@ -818,7 +818,6 @@ int amdgpu_ttm_tt_get_user_pages(struct amdgpu_bo *bo, struct page **pages) 0 : range->flags[HMM_PFN_WRITE]; range->pfn_flags_mask = 0; range->pfns = pfns; - range->page_shift = PAGE_SHIFT; range->start = start; range->end = start + ttm->num_pages * PAGE_SIZE; diff --git a/drivers/gpu/drm/nouveau/nouveau_svm.c b/drivers/gpu/drm/nouveau/nouveau_svm.c in...

.../amdgpu/amdgpu_ttm.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c index 71d6e7087b0b..8bf79288c4e2 100644 --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c @@ -818,7 +818,6 @@ int amdgpu_ttm_tt_get_user_pages(struct amdgpu_bo *bo, struct page **pages) 0 : range->flags[HMM_PFN_WRITE]; range->pfn_flags_mask = 0; range->pfns = pfns; - range->page_shift = PAGE_SHIFT; range->start = start; range->end = start + ttm->num_pages * PAGE_SIZE; diff --git a/drivers/gpu/drm/nouveau/nouveau_svm.c b/drivers/gpu/drm/nouveau/nouveau_svm.c in...

...ee is also available at: git://git.infradead.org/users/hch/misc.git hmm-cleanups.2 Gitweb: http://git.infradead.org/users/hch/misc.git/shortlog/refs/heads/hmm-cleanups.2 Changes since v1: - fix the cover letter subject - improve various patch descriptions - use svmm->mm in nouveau_range_fault - inverse the hmask field when using it - select HMM_MIRROR instead of making it a user visible option

...A. P. Cunha wrote: > > Hello! > Any opinion on that? > Thank you > > > Em 13-07-2016 10:52, Carlos A. P. Cunha escreveu: >> >> Thank you for the explanation. >> Yes, it was a mistake to leave my two faxias that way, by the ID >> exchange reason the low range will leave as it was to have no problems >> idmap config SERVERAD: range = 5000-33554431 >> >> The range of up'm thinking of changing to something >> idmap config *: range = 2000-4500 >> >> Not to be superimposed. >> >> But it will it not cause pr...

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...

Thank you for the explanation. Yes, it was a mistake to leave my two faxias that way, by the ID exchange reason the low range will leave as it was to have no problems idmap config SERVERAD: range = 5000-33554431 The range of up'm thinking of changing to something idmap config *: range = 2000-4500 Not to be superimposed. But it will it not cause problem ids trading again? Since it was before both inciado in 50000...

...o 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 return the valid state from hmm_range_unregister - additional nouveau cleanups

...m/BUILD/syslinux-3.11/opt/nasm/bin /nasm /home/axel/p/rpm/BUILD/syslinux-3.11/opt/nasm/bin/nasm -f bin -DDATE_STR="'0x43115316'" -DHEXDATE="0x43115316" \ -DMAP=pxelinux.map -l pxelinux.lst -o pxelinux.bin pxelinux.asm pxelinux.asm:356: error: short jump is out of range pxelinux.asm:381: error: short jump is out of range pxelinux.asm:409: error: short jump is out of range pxelinux.asm:414: error: short jump is out of range pxelinux.asm:780: error: short jump is out of range ui.inc:26: error: short jump is out of range ui.inc:30: error: short jump is out of range u...

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 a result of Jason's sugges...

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

...oid the dialog box would be appreciated. The macro is below. It's your basic, send-to-R, run R, retrieve-from-R macro. Call Rinterface.StartRServer Call Rinterface.RRun("rm(list = ls())") Call Rinterface.RRun("dev.off()") Call Rinterface.PutArray("mat1", Range("DATA_INPUT_OUTPUT!B7:I506")) Call Rinterface.PutArray("mat2", Range("DATA_INPUT_OUTPUT!J7:Q506")) Call Rinterface.PutArray("cpd", Range("DATA_INPUT_OUTPUT!A7:A506")) Call Rinterface.PutArray("name_of_assay_one", Range("D...

I got it, so it must have been the problem .. Strange that changed it more than one month at least. Having these values now, how do you think I do? Leave it or change at least the idmap config * values: range? I understand the parameters: idmap config *: range = Range of the Ids are User system idmap config SERVERAD: range: DC User Range Thank you...