It could be used to implement very hard to crack DRM schemes as well...
actually, no not really: the memory encryption feature hides information from memory contents leaking to outside of the OS controlled domain, but keeps it fully accessible within it – it has to for normal operation of the computer. So it can't and won't, e.g. hide the memory from a driver running within the OS on ring 0.
Same for encrypted virtualization: it won't hide the information from the host itself.
The only way I can see DRM being implemented with this is having a DRM-protected application running in a an encrypted virtual machine. For one kind of DRM, the stuff for games, which want to use "actual graphics", it's helluva problematic. While for the other kind of DRM, music and movies, that just introduces a problem of "we still need to get the decrypted content outside of the VM, to the hypervisor / underlying OS, so it could actually present it to the user."
And even if someone finds some convulated way to make use of these for DRM, due to the nature of the tech and since these both features interact with the OSes running on the hardware in a non-trivial way, it's simply an option one can, nay,
has to be able to disable before boot. (Or more like, have to be explicitly enabled by the user before boot, likely in the form of BIOS/UEFI/whatever settings, lest all hell breaks loose if the software doesn't support it)
[...]
That's not Zen so, either the picture is bull or Beema already has this feature and it's not new to Zen.
What these had/have is called a TrustedZone, which is this just slightly useful thing mainly used by ARM platforms, which AMD licensed from aforementioned ARM.
What Zen is getting is this
plus a whole lotta more and these additional features are not provided nor available on the TrustedZone dohicky.