if you disable CONFIG_COMPAT_VDSO then you'll actually be able to enable various non-exec implementations under NOEXEC (right now you have nothing, hence the paxtest results). while you're at it you probably want to enable HIGHMEM64G support as well so that PaX would make use of the NX bit.
when 64gb/PAE enabled, some tests begin to segfault, but not java. i assume it is not normal PAX behaviour
it's the NX bit in action that the vanilla kernel also makes use of for some time now.
are there any special requirements on userspace ? Asking, because i can't find any "step by step" documentation on how to install pax to generic distribution.
well, for 'full' protection you want to get rid of text relocations (that's quite some work, check the gentoo bugzilla where i posted many patches over the years), then there's the PaX feature control stuff, either paxctl or RBAC. also if you want to have main executable randomization, you'll have to recompile those apps as PIE, which can be done in different ways, depending on how much you want to tweak your toolchain (gcc specs file, per-package makefiles, distro specific build tool, etc).