CVS log for src/sys/arch/amd64/include/asan.h

Up to [cvs.NetBSD.org] / src / sys / arch / amd64 / include

Request diff between arbitrary revisions

Keyword substitution: kv
Default branch: MAIN

amd64/asan.h, amd64/msan.h: Add include guards.

Sprinkle "#include <machine/pmap_private.h>", kernel ALL/amd64
compiles again.

x86: Split bootspace out of x86/pmap.h into new x86/bootspace.h.

kasan: fix the copyright notices

Round of uvm.h cleanup.

The poorly named uvm.h is generally supposed to be for uvm-internal
users only.

- Narrow it to files that actually need it -- mostly files that need
  to query whether curlwp is the pagedaemon, which should maybe be
  exposed by an external header.

- Use uvm_extern.h where feasible and uvm_*.h for things not exposed
  by it.  We should split up uvm_extern.h but this will serve for now
  to reduce the uvm.h dependencies.

- Use uvm_stat.h and #ifdef UVMHIST uvm.h for files that use
  UVMHIST(ubchist), since ubchist is declared in uvm.h but the
  reference evaporates if UVMHIST is not defined, so we reduce header
  file dependencies.

- Make uvm_device.h and uvm_swap.h independently includable while
  here.

ok chs@

Rename __MD_CANONICAL_BASE -> __MD_KERNMEM_BASE for clarity.

Call kasan_early_init earlier, to unbreak KASAN after the recent RNG
changes. Will also prevent further trouble.

Merge the bouyer-xenpvh branch, bringing in Xen PV drivers support under HVM
guests in GENERIC.
Xen support can be disabled at runtime with
boot -c
disable hypervisor

Sync with HEAD

Sync with HEAD

Use large pages for the kASan shadow, same as kMSan.

Sync with HEAD

file asan.h was added on branch phil-wifi on 2019-06-10 22:05:47 +0000

Start replacing the x86 PTE bits.

Add more symbols to the unwinder, in case we get a KASAN message inside
an exception handler.

Sync with HEAD, resolve a couple of conflicts

file asan.h was added on branch pgoyette-compat on 2018-11-26 01:52:17 +0000

Move the MI parts of KASAN into kern/subr_asan.c. This file includes
machine/asan.h, which contains the MD functions. We use an include rather
than a plain C file, because we want GCC to optimize/inline some functions
into one single block.

The amd64 MD parts of KASAN are moved accordingly.

The naming convention we use is:

	kasan_*
		a generic kasan object, declared in subr_asan.c
	kasan_md_*
		an MD kasan object, declared in machine/asan.h, and used
		in subr_asan.c
	__md_*
		an MD object, declared in machine/asan.h, and not used
		outside

Overall this makes it easier to add KASAN support on more architectures.

Discussed with several people.