diff options
| author | Jan Beulich <jbeulich@suse.com> | 2013-01-23 14:14:34 +0100 |
|---|---|---|
| committer | Jan Beulich <jbeulich@suse.com> | 2013-01-23 14:14:34 +0100 |
| commit | 53a4e820f2888b1c7fcac6cc65c5ce854a2ff1ea (patch) | |
| tree | e8eb111683587f5a494d743ee61093272b2b0bdb /xen/arch/x86/hvm/rtc.c | |
| parent | f697f2fc18f11c28cffc61f39025c3bfa92d376d (diff) | |
| download | xen-53a4e820f2888b1c7fcac6cc65c5ce854a2ff1ea.tar.gz xen-53a4e820f2888b1c7fcac6cc65c5ce854a2ff1ea.tar.bz2 xen-53a4e820f2888b1c7fcac6cc65c5ce854a2ff1ea.zip | |
tmem: partial adjustments for x86 16Tb support
Despite the changes below, tmem still has code assuming to be able to
directly access all memory, or mapping arbitrary amounts of not
directly accessible memory. I cannot see how to fix this without
converting _all_ its domheap allocations to xenheap ones. And even then
I wouldn't be certain about there not being other cases where the "all
memory is always mapped" assumption would be broken. Therefore, tmem
gets disabled by the next patch for the time being if the full 1:1
mapping isn't always visible.
Signed-off-by: Jan Beulich <jbeulich@suse.com>
Acked-by: Dan Magenheimer <dan.magenheimer@oracle.com>
Acked-by: Keir Fraser <keir@xen.org>
Diffstat (limited to 'xen/arch/x86/hvm/rtc.c')
0 files changed, 0 insertions, 0 deletions