On 06/26/2015 10:52 AM, Jan Beulich wrote:
On 26.06.15 at 16:34, <ian.campb...@citrix.com> wrote:
I did this using rdmsr from mst-tools instead, running on a native
kernel gave:
# for i in $(seq 0 31) ;do rdmsr -p $i MSR_K8_TOP_MEM2; done
0
[...]
0
Is MSR_K8_TOP_MEM2 defined somewhere in the shell?
Just to make sure, could you use explicit address, i.e.
for i in $(seq 0 31) ;do rdmsr -p $i 0xc001001d; done
(and if they are still all zeroes, can you read 0xc0010010 (SYSCFG) as
well?)
-boris
Uniformly uncachable for everything above 4Gb then. And I suppose
you already checked that there's no BIOS update available?
I'm not sure if it would be reasonable for us to work around this.
Suravee, Aravind - do you (or colleagues of yours) have any
experience with systems mis-configured like this one?
Otoh I'm then pretty confused by your E820 clipping experiment not
having yielded any better results. I'm starting to suspect two
problems...
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
