Displaying 9 results from an estimated 9 matches for "in_rang".
Did you mean:
in_range
2014 Aug 20
2
[LLVMdev] LLVM CreateStructGEP type assert error
...art -------------------------------
#define BLOCK_SIZE 16
//dlowell's type
#define BUFFER_LEN 0x100000
typedef struct RB{
unsigned int x;
unsigned int y;
int z[BUFFER_LEN];
unsigned int xx[BUFFER_LEN];
unsigned int yy[BUFFER_LEN];
float zz[BUFFER_LEN];
} RBr_t;
#define IN_RANGE(x, min, max) ((x)>=(min) && (x)<=(max))
__kernel void hotspot( int iteration, //number of iteration
global float *power, //power input
global float *temp_src, //temperature input/output...
2019 Oct 30
0
[PATCH v2 09/15] xen/gntdev: use mmu_range_notifier_insert
...&priv->lock);
> }
> vma->vm_private_data = NULL;
> gntdev_put_map(priv, map);
> @@ -477,109 +462,44 @@ static const struct vm_operations_struct gntdev_vmops = {
>
> /* ------------------------------------------------------------------ */
>
> -static bool in_range(struct gntdev_grant_map *map,
> - unsigned long start, unsigned long end)
> -{
> - if (!map->vma)
> - return false;
> - if (map->vma->vm_start >= end)
> - return false;
> - if (map->vma->vm_end <= start)
> - return false;
> -
> - return...
2019 Oct 28
1
[PATCH v2 09/15] xen/gntdev: use mmu_range_notifier_insert
...map->vma = NULL;
- mutex_unlock(&priv->lock);
}
vma->vm_private_data = NULL;
gntdev_put_map(priv, map);
@@ -477,109 +462,44 @@ static const struct vm_operations_struct gntdev_vmops = {
/* ------------------------------------------------------------------ */
-static bool in_range(struct gntdev_grant_map *map,
- unsigned long start, unsigned long end)
-{
- if (!map->vma)
- return false;
- if (map->vma->vm_start >= end)
- return false;
- if (map->vma->vm_end <= start)
- return false;
-
- return true;
-}
-
-static int unmap_if_in_range(struct g...
2011 Sep 06
17
ext4 BUG in dom0 Kernel 2.6.32.36
...ext4_da_sritepages->mpage_da_map_blocks->ext4_get_blocks->ext4_ext_get_blocks->
ext4_ext_handle_uninitialized_extents->ext4_ext_convert_to_initialized->ext4_ext_insert_extent
if ext4_ext_handle_uninitialized_extents is called, then line 3306 must be satisfied.
that is we have in_range(iblock, ee_block, ee_len) = true.
so iblock >= ee_block
fs/ext4/extents.c
3306 <+++<+++if (in_range(iblock, ee_block, ee_len)) {
3307 <+++<+++<+++newblock = iblock - ee_blo...
2014 Aug 20
2
[LLVMdev] LLVM CreateStructGEP type assert error
If I do M.dump(), at the top of the output I have:
%struct.RB = type opaque
Further down I have:
@.str18 = internal addrspace(2) constant [13 x i8] c"RB_t*\00"
However nowhere does it dump the full struct type when I call "M.dump()". I have it explicitly defined above the kernel in the kernel file, but LLVM doesn't seem to pick it up.
Opaque is a placeholder until it
2016 Sep 16
0
[ANNOUNCE] xorg-server 1.18.99.2
...e xf86_reload_cursors v2
glamor: Call eglBindAPI after eglInitialize
xwayland: Call eglBindAPI after eglInitialize
xfree86/modes: Fix HW cursor clipping for driverIsPerformingTransform (v2)
xfree86/modes: Disambiguate driverIsPerformingTransform
xfree86/modes: Simplify in_range logic in xf86_crtc_set_cursor_position
dix: Work around non-premultiplied ARGB cursor data
glamor: Translate solid text background region after clipping
xfree86/modes: Move gamma initialization to xf86RandR12Init12 v2
xfree86/modes: Remove xf86RandR12CrtcGetGamma
xfre...
2008 Sep 04
4
[PATCH 0/3] ocfs2: Switch over to JBD2.
ocfs2 currently uses the Journaled Block Device (JBD) for its
journaling. This is a very stable and tested codebase. However, JBD
is limited by architecture to 32bit block numbers. This means an ocfs2
filesystem is limited to 2^32 blocks. With a 4K blocksize, that's 16TB.
People want larger volumes.
Fortunately, there is now JBD2. JBD2 adds 64bit block number support
and some other
2019 Oct 28
32
[PATCH v2 00/15] Consolidate the mmu notifier interval_tree and locking
From: Jason Gunthorpe <jgg at mellanox.com>
8 of the mmu_notifier using drivers (i915_gem, radeon_mn, umem_odp, hfi1,
scif_dma, vhost, gntdev, hmm) drivers are using a common pattern where
they only use invalidate_range_start/end and immediately check the
invalidating range against some driver data structure to tell if the
driver is interested. Half of them use an interval_tree, the others
2019 Nov 12
20
[PATCH hmm v3 00/14] Consolidate the mmu notifier interval_tree and locking
From: Jason Gunthorpe <jgg at mellanox.com>
8 of the mmu_notifier using drivers (i915_gem, radeon_mn, umem_odp, hfi1,
scif_dma, vhost, gntdev, hmm) drivers are using a common pattern where
they only use invalidate_range_start/end and immediately check the
invalidating range against some driver data structure to tell if the
driver is interested. Half of them use an interval_tree, the others