x86/AMD: make HT range dynamic for Fam17 and up
authorJan Beulich <jbeulich@suse.com>
Fri, 19 Nov 2021 08:38:09 +0000 (09:38 +0100)
committerJan Beulich <jbeulich@suse.com>
Fri, 19 Nov 2021 08:38:09 +0000 (09:38 +0100)
commit0c3fde7b7e920fb5c20747567c249714fab57282
tree8aa127f9eeb02607cea488f938e80e9036a19544
parent7c957ea6125a1510baee4e01413451612c29312b
x86/AMD: make HT range dynamic for Fam17 and up

At the time of d838ac2539cf ("x86: don't allow Dom0 access to the HT
address range") documentation correctly stated that the range was
completely fixed. For Fam17 and newer, it lives at the top of physical
address space, though.

To correctly determine the top of physical address space, we need to
account for their physical address reduction, hence the calculation of
paddr_bits also gets adjusted.

While for paddr_bits < 40 the HT range is completely hidden, there's no
need to suppress the range insertion in that case: It'll just have no
real meaning.

Reported-by: Igor Druzhinin <igor.druzhinin@citrix.com>
Signed-off-by: Jan Beulich <jbeulich@suse.com>
Reviewed-by: Roger Pau Monné <roger.pau@citrix.com>
master commit: d6e38eea2d806c53d976603717aebf6e5de30a1e
master date: 2021-10-19 10:04:13 +0200
xen/arch/x86/cpu/common.c
xen/arch/x86/dom0_build.c