From: Alex Williamson <alex.williamson@hp.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Jan Beulich <JBeulich@novell.com>
Subject: Re: Tagging Xen 4.0.0 first release candidate
Date: Tue, 5 Jan 2010 09:00:55 -0700 [thread overview]
Message-ID: <7162ab21001050800n7799e2bh998f37d62c29d45@mail.gmail.com> (raw)
In-Reply-To: <C768B17A.5734%keir.fraser@eu.citrix.com>
On Tue, Jan 5, 2010 at 2:06 AM, Keir Fraser <keir.fraser@eu.citrix.com> wrote:
> On 05/01/2010 08:56, "Jan Beulich" <JBeulich@novell.com> wrote:
>
>> In any case I'm of the opinion that the tools limitations with the old
>> ioctl should be eliminated before 4.0 gets released - I had hoped
>> that someone with better knowledge of the tools than I have
>> would approach this, but since no-one showed up I'll try to.
>
> It's a bit late for 4.0.0 really. The lack of interest is probably the lack
> of people hitting the 43-bit limitation built into the current interface.
> Just about noone is anywhere near close to it.
Perhaps due to the lack of x86 processors supporting more than 40-bits
of physical address space that are currently on the market. But we
know that's going to change fairly shortly and x86 will finally get
support for more than 1TB. That opens the doors for hardware vendors
to create interesting configurations and maybe not worry so much about
compressing the address space into a contiguous block. If Xen can't
support at least a 44-bit physical address space within the 4.x
lifetime, it could become a serious limiting factor. It seems rather
shortsighted not to prepare for it now, especially given the
opportunity we have at a major version break. Thanks,
Alex
next prev parent reply other threads:[~2010-01-05 16:00 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-05 6:42 Tagging Xen 4.0.0 first release candidate Keir Fraser
2010-01-05 8:56 ` Jan Beulich
2010-01-05 9:06 ` Keir Fraser
2010-01-05 16:00 ` Alex Williamson [this message]
2010-01-05 16:06 ` Keir Fraser
2010-01-19 13:57 ` Tagging Xen 4.0.0 first release candidate, 44-bit address space support Pasi Kärkkäinen
2010-01-19 14:02 ` Keir Fraser
2010-01-19 14:22 ` Pasi Kärkkäinen
2010-01-06 13:50 ` Tagging Xen 4.0.0 first release candidate / pygrub dom0 caching bug Pasi Kärkkäinen
2010-01-21 12:28 ` Pasi Kärkkäinen
2010-01-21 15:39 ` Jan Beulich
2010-01-21 18:44 ` Daniel Stodden
2010-01-21 19:16 ` Daniel Stodden
2010-01-21 19:37 ` Ian Campbell
2010-01-21 21:01 ` Pasi Kärkkäinen
2010-01-21 21:53 ` Daniel Stodden
2010-01-27 9:27 ` Pasi Kärkkäinen
2010-01-28 19:34 ` Daniel Stodden
2010-01-06 15:00 ` Tagging Xen 4.0.0 first release candidate Christian Tramnitz
2010-01-06 21:42 ` Ian Pratt
2010-01-06 21:52 ` Pasi Kärkkäinen
2010-01-07 11:51 ` Pasi Kärkkäinen
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=7162ab21001050800n7799e2bh998f37d62c29d45@mail.gmail.com \
--to=alex.williamson@hp.com \
--cc=JBeulich@novell.com \
--cc=keir.fraser@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
/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).