Finish merging from head, messed up in previous attempt

Merge from head

Merge r286744-r287584 from head.

Merge from HEAD

Merge ^/head r286697 through r286857.

Stop describing an acquire operation as a read barrier and a release
operation as a write barrier. That description has never been correct,
and it has caused confusion. An acquire operation orders

Stop describing an acquire operation as a read barrier and a release
operation as a write barrier. That description has never been correct,
and it has caused confusion. An acquire operation orders writes as well
as reads, and a release operation orders reads as well as writes.

Also, explicitly say that a thread doesn't see its own accesses being
reordered. The reordering of a thread's accesses is only (potentially)
visible to another thread. Thus, memory barriers need only be used to
control the ordering of accesses between threads, not within a thread.

Reviewed by: bde, kib
Discussed with: jhb
MFC after: 1 week

show more ...

Catch up with head, primarily for the 1.14.4.0 firmware.

Merge ^/head r286422 through r286684.

Revise the text about the atomicity of the defined operations across
multiple processors. In particular, clearly state that the operations
are always atomic when they are applied to the default memo

Revise the text about the atomicity of the defined operations across
multiple processors. In particular, clearly state that the operations
are always atomic when they are applied to the default memory type
that is used by the kernel (and applications).

Reviewed by: kib, jhb (an earlier version)
MFC after: 1 week

show more ...

Merge ^/head r284644 through r284736.

Catch up with HEAD (r280229-r284686).

The barriers, provided by _acq and _rel atomics, are acquire and
release barriers, not read and write barriers. They fence all memory
accesses from the respective side, not limited by the kind of
op

The barriers, provided by _acq and _rel atomics, are acquire and
release barriers, not read and write barriers. They fence all memory
accesses from the respective side, not limited by the kind of
operation.

Reviewed by: jhb
Sponsored by: The FreeBSD Foundation
MFC after: 1 week

show more ...

IFC @r269962

Submitted by: Anish Gupta (akgupt3@gmail.com)

Merge head from 7/28

Sync to HEAD@r269943.

Remove ia64.

This includes:
o All directories named *ia64*
o All files named *ia64*
o All ia64-specific code guarded by __ia64__
o All ia64-specific makefile logic
o Mention of ia64 in com

Remove ia64.

This includes:
o All directories named *ia64*
o All files named *ia64*
o All ia64-specific code guarded by __ia64__
o All ia64-specific makefile logic
o Mention of ia64 in comments and documentation

This excludes:
o Everything under contrib/
o Everything under crypto/
o sys/xen/interface
o sys/sys/elf_common.h

Discussed at: BSDcan

show more ...

Merge head r233826 through r256722.

IFC @256277

Approved by: ken (mentor)

IFC @ r255692

Comment out IA32_MISC_ENABLE MSR access - this doesn't exist on AMD.
Need to sort out how arch-specific MSRs will be handled.

Merge from head

IFC @ r255209

MFC

Minor mdoc nit.

IFC.

Implement atomic_swap() and atomic_testandset().

Reviewed by: arch, bde, jilles, kib