From: Dan Magenheimer <dan.magenheimer@oracle.com>
To: Jan Beulich <JBeulich@suse.com>, xen-devel <xen-devel@lists.xen.org>
Cc: Konrad Wilk <konrad.wilk@oracle.com>
Subject: Re: [PATCH 10/11] tmem: partial adjustments for x86 16Tb support
Date: Tue, 22 Jan 2013 09:55:43 -0800 (PST) [thread overview]
Message-ID: <d691ee94-f21b-47e7-82fe-67a728f92089@default> (raw)
In-Reply-To: <50FE7E9F02000078000B8351@nat28.tlf.novell.com>
> From: Jan Beulich [mailto:JBeulich@suse.com]
> Sent: Tuesday, January 22, 2013 8:32 AM
> To: xen-devel; Dan Magenheimer
> Cc: Konrad Wilk
> Subject: RE: [Xen-devel] [PATCH 11/11] x86: support up to 16Tb
>
> > Acked-by: Dan Magenheimer <dan.magenheimer@oracle.com>
>
> Hmm, an ack on this patch is sort of unexpected from you; I
> would have hoped you would ack patch 10...
Heh. I was intrigued by the new domain_page_map_to_mfn()
and wanted to look deeper before acking patch 10. So...
> From: Jan Beulich [mailto:JBeulich@suse.com]
> Subject: [PATCH 10/11] 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>
IIUC, all the metadata will need to be allocated from the xenheap
and all "wholepage" accesses will need some kind of wrapper.
This will get messier with compression/deduplication, but
I'm thinking it will still be doable... sometime in the future
if/when users want/need memory overcommit on huge RAM systems.
In any case...
Acked-by: Dan Magenheimer <dan.magenheimer@oracle.com>
next prev parent reply other threads:[~2013-01-22 17:55 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-22 10:45 [PATCH 00/11] x86: support up to 16Tb Jan Beulich
2013-01-22 10:50 ` [PATCH 02/11] x86: extend frame table virtual space Jan Beulich
2013-01-22 10:50 ` [PATCH 03/11] x86: re-introduce map_domain_page() et al Jan Beulich
2013-01-22 10:51 ` [PATCH 04/11] x86: properly use map_domain_page() when building Dom0 Jan Beulich
2013-01-22 10:52 ` [PATCH 05/11] x86: consolidate initialization of PV guest L4 page tables Jan Beulich
2013-01-22 10:53 ` [PATCH 06/11] x86: properly use map_domain_page() during domain creation/destruction Jan Beulich
2013-01-22 10:55 ` [PATCH 07/11] x86: properly use map_domain_page() during page table manipulation Jan Beulich
2013-01-22 10:55 ` [PATCH 08/11] x86: properly use map_domain_page() in nested HVM code Jan Beulich
2013-01-22 10:56 ` [PATCH 09/11] x86: properly use map_domain_page() in miscellaneous places Jan Beulich
2013-01-22 10:57 ` [PATCH 10/11] tmem: partial adjustments for x86 16Tb support Jan Beulich
2013-01-22 17:55 ` Dan Magenheimer [this message]
2013-01-22 10:57 ` [PATCH 11/11] x86: support up to 16Tb Jan Beulich
2013-01-22 15:20 ` Dan Magenheimer
2013-01-22 15:31 ` Jan Beulich
2013-01-22 10:58 ` [PATCH 12/11] x86: debugging code for testing 16Tb support on smaller memory systems Jan Beulich
2013-01-23 14:26 ` [PATCH v2] " Jan Beulich
2013-01-23 15:18 ` Keir Fraser
2013-01-24 11:36 ` Tim Deegan
2013-01-24 12:23 ` Jan Beulich
2013-01-24 12:36 ` Tim Deegan
2013-01-22 20:13 ` [PATCH 00/11] x86: support up to 16Tb Keir Fraser
2013-01-23 9:33 ` Keir Fraser
2013-01-23 9:56 ` Jan Beulich
2013-01-23 10:16 ` Keir Fraser
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d691ee94-f21b-47e7-82fe-67a728f92089@default \
--to=dan.magenheimer@oracle.com \
--cc=JBeulich@suse.com \
--cc=konrad.wilk@oracle.com \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).