search for: atomic_

...dispnv50/disp.c +++ b/drivers/gpu/drm/nouveau/dispnv50/disp.c @@ -455,7 +455,7 @@ nv50_outp_get_old_connector(struct nouveau_encoder *outp, * DAC *****************************************************************************/ static void -nv50_dac_disable(struct drm_encoder *encoder, struct drm_atomic_state *state) +nv50_dac_atomic_disable(struct drm_encoder *encoder, struct drm_atomic_state *state) { struct nouveau_encoder *nv_encoder = nouveau_encoder(encoder); struct nv50_core *core = nv50_disp(encoder->dev)->core; @@ -467,7 +467,7 @@ nv50_dac_disable(struct drm_encoder *encoder, st...

...when loading/storing pointers or values up to the native width of the machine). I believe that's the case here, for virtio, for example. Perhaps we can add new accessors that are supposed to guarantee that, into which we can drop appropriate warnings. Naming will be problematic; calling them ATOMIC_* makes tham sound like they work on atomic_t. That and I have no idea how to ensure correct usage tree-wide; I'm not sure if/how Coccinelle can help. Peter, thoughts? Thanks, Mark.

...when loading/storing pointers or values up to the native width of the machine). I believe that's the case here, for virtio, for example. Perhaps we can add new accessors that are supposed to guarantee that, into which we can drop appropriate warnings. Naming will be problematic; calling them ATOMIC_* makes tham sound like they work on atomic_t. That and I have no idea how to ensure correct usage tree-wide; I'm not sure if/how Coccinelle can help. Peter, thoughts? Thanks, Mark.

...s, which clang lowers directly to atomic IR instructions. Then, the llvm atomic IR instructions themselves can sometimes emit libcalls to __sync_* library functions (which are basically undocumented, and users are often responsible for implementing themselves if they need it). There's the new __atomic_* builtins, which clang will, depending on size and alignment and target, lower either to a libcall to a "standardized-by-GCC <https://gcc.gnu.org/wiki/Atomic/GCCMM/LIbrary>" __atomic_* library function (implemented by libatomic), or, to the atomic IR instructions. (Also covered by t...

On Fri, Nov 25, 2016 at 12:23:56PM +0000, Mark Rutland wrote: > Naming will be problematic; calling them ATOMIC_* makes tham sound like > they work on atomic_t. That and I have no idea how to ensure correct > usage tree-wide; I'm not sure if/how Coccinelle can help. > > Peter, thoughts? Something like so perhaps? --- #ifdef CONFIG_DEBUG_ATOMIC_SLEEP #define WARN_SINGLE_COPY_ALIGNMENT(ptr)...

On Mon, Mar 11, 2019 at 02:07:16PM +0100, Gerd Hoffmann wrote: > Hi, > > > > > static void bochs_crtc_atomic_flush(struct drm_crtc *crtc, > > > > struct drm_crtc_state *old_crtc_state) > > > > { > > > > @@ -66,6 +71,7 @@ static const struct drm_crtc_funcs bochs_crtc_funcs = { > > > > static const struct drm_crtc_helper_funcs bochs_helper_funcs = {...

...p, _only_ when needed modetest: add and use bo_fb_create() helper modetest: remove drmMode{,Plane}Res modetest: close the device on exit modetest: introduce and use get_crtc_by_id() and get_crtc_mask() modetest: get the crtc_id from the pipe_arg modetest: unify {,atomic_}set_mode() modetest: move pipe_resolve_connectors() further up modetest: push pipe_resolve_connectors() to set_mode modetest: factor out atomic pageflip test modetest: don't error out of final AtomicCommit modetest: reorder atomic path alike the non-atomic mo...

Hi, > > > static void bochs_crtc_atomic_flush(struct drm_crtc *crtc, > > > struct drm_crtc_state *old_crtc_state) > > > { > > > @@ -66,6 +71,7 @@ static const struct drm_crtc_funcs bochs_crtc_funcs = { > > > static const struct drm_crtc_helper_funcs bochs_helper_funcs = { > > > .mo...

Hi, > > > static void bochs_crtc_atomic_flush(struct drm_crtc *crtc, > > > struct drm_crtc_state *old_crtc_state) > > > { > > > @@ -66,6 +71,7 @@ static const struct drm_crtc_funcs bochs_crtc_funcs = { > > > static const struct drm_crtc_helper_funcs bochs_helper_funcs = { > > > .mo...

On Thu, Nov 24, 2016 at 10:36:58PM +0200, Michael S. Tsirkin wrote: > On Thu, Nov 24, 2016 at 10:25:11AM +0000, Mark Rutland wrote: > > For several reasons, it would be beneficial to kill off ACCESS_ONCE() > > tree-wide, in favour of {READ,WRITE}_ONCE(). These work with aggregate types, > > more obviously document their intended behaviour, and are necessary for tools > >

On Thu, Nov 24, 2016 at 10:36:58PM +0200, Michael S. Tsirkin wrote: > On Thu, Nov 24, 2016 at 10:25:11AM +0000, Mark Rutland wrote: > > For several reasons, it would be beneficial to kill off ACCESS_ONCE() > > tree-wide, in favour of {READ,WRITE}_ONCE(). These work with aggregate types, > > more obviously document their intended behaviour, and are necessary for tools > >

...omic IR instructions. Then, the llvm atomic IR instructions > themselves can sometimes emit libcalls to __sync_* library > functions (which are basically undocumented, and users are often > responsible for implementing themselves if they need it). > 2. There's the new __atomic_* builtins, which clang will, depending > on size and alignment and target, lower either to a libcall to a > "standardized-by-GCC > <https://gcc.gnu.org/wiki/Atomic/GCCMM/LIbrary>" __atomic_* > library function (implemented by libatomic), or, to the atomic...

...orrect sampler bind index for ld_raw and ld_structured. d3d11/tests: Add test for ld_structured instruction. wined3d: Allow swizzle on vThreadIDInGroupFlattened register. wined3d: Use GL_ARB_shading_language_420pack for swizzle operations on scalars. wined3d: Implement [imm_]atomic_{umax, umin} instructions for unsigned integers. wined3d: Implement [imm_]atomic_{imax, imin} instructions for signed integers. wined3d: Do not crash when attempting to issue draw call with no attachments. wined3d: Pass wined3d_caps_gl_ctx to driver quirk match() function. wi...

...ructions. Then, the llvm atomic IR > instructions themselves can sometimes emit libcalls to __sync_* > library functions (which are basically undocumented, and users > are often responsible for implementing themselves if they need > it). > 2. There's the new __atomic_* builtins, which clang will, > depending on size and alignment and target, lower either to a > libcall to a " standardized-by-GCC " __atomic_* library function > (implemented by libatomic), or, to the atomic IR instructions. > (Also covered by the same code is...

...pm status on timeout lib/aux: Ensure swap space prior to suspend to disk Emil Velikov (1): test/core_setmaster: new test for drop/set master semantics Guillaume Tucker (6): meson: add libatomic dependency gitlab-ci: add libatomic to docker images i915/gem_create: use atomic_* instead of __sync_* tests/sw_sync: use atomic_* instead of __sync_* gitlab-ci: add build for MIPS gitlab-ci: add tests for MIPS Imre Deak (31): tests/kms_properties: Fix upper bound of 'max bpc' range lib/rendercopy: Add AUX page table support tests/gem...

...classes. include: Add definition for FILE_ID_INFORMATION. kernel32: Added implementation of FileIdInfo for GetFileInformationByHandleEx. Józef Kucia (55): ddraw: Implement D3DOP_TEXTURELOAD. ddraw/tests: Add basic test for D3DOP_TEXTURELOAD. wined3d: Recognize SM5 imm_atomic_iadd opcode. wined3d: Implement applying state for compute pipeline. wined3d: Group compute states together. wined3d: Allow passing compute states to device_invalidate_state(). wined3d: Use more suitable bind target for SRV/UAV buffers. d3d11/tests: Add test for interle...

Hi all, Although [smp_]read_barrier_depends() became part of READ_ONCE() in commit 76ebbe78f739 ("locking/barriers: Add implicit smp_read_barrier_depends() to READ_ONCE()"), it still limps on in the Linux memory model with the sinister hope of attracting innocent new users so that it becomes impossible to remove altogether. Let's strike before it's too late: there's only

Hi all, This is version three of the patches I previously posted here: v1: https://lore.kernel.org/lkml/20191108170120.22331-1-will at kernel.org/ v2: https://lore.kernel.org/r/20200630173734.14057-1-will at kernel.org Changes since v2 include: * Actually add the barrier in READ_ONCE() for Alpha! * Implement Alpha's smp_load_acquire() using __READ_ONCE(), rather than the other

Hi everyone, This is the long-awaited version two of the patches I previously posted in November last year: https://lore.kernel.org/lkml/20191108170120.22331-1-will at kernel.org/ I ended up parking the series while the READ_ONCE() implementation was being overhauled, but with that merged during the recent merge window and LTO patches being posted again [1], it was time for a refresh. The

Hi everyone, This is the long-awaited version two of the patches I previously posted in November last year: https://lore.kernel.org/lkml/20191108170120.22331-1-will at kernel.org/ I ended up parking the series while the READ_ONCE() implementation was being overhauled, but with that merged during the recent merge window and LTO patches being posted again [1], it was time for a refresh. The