From: Keir Fraser <keir.xen@gmail.com>
To: David Vrabel <david.vrabel@citrix.com>
Cc: xen-devel@lists.xen.org
Subject: Re: [ANNOUNCE] Xen x86 32-bit hypervisor end of life after 4.2
Date: Mon, 10 Sep 2012 17:55:27 +0100 [thread overview]
Message-ID: <CC73DA0F.3E425%keir.xen@gmail.com> (raw)
In-Reply-To: <504E1458.70606@citrix.com>
On 10/09/2012 17:24, "David Vrabel" <david.vrabel@citrix.com> wrote:
> On 09/09/12 12:11, Keir Fraser wrote:
>> Folks,
>>
>> With 64-bit support well established in the x86 world these days, the number
>> of x86 production environments that cannot run a 64-bit hypervisor is pretty
>> much nil. Maintaining the 32-bit x86 port, and implementing new features for
>> it, is an ongoing development burden which could be more usefully directed
>> elsewhere. Therefore, 32-bit x86 will be considered obsolete in the 4.3
>> development branch, and removed.
>
> I have some tracing patches that have some 32-bit/64-bit #ifdef'ery.
> Would you prefer them posted now, or deferred until 32-bit is gone?
If it's not too intricate then post them now, and we'll strip out the 32-bit
parts later. I don't think we should hold up pending patches for this.
Although I'm holding back some further development in anticipation of it. :)
-- Keir
> David
prev parent reply other threads:[~2012-09-10 16:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-09 11:11 [ANNOUNCE] Xen x86 32-bit hypervisor end of life after 4.2 Keir Fraser
2012-09-10 14:00 ` Keir Fraser
2012-09-10 14:16 ` Ian Jackson
2012-09-10 14:23 ` Keir Fraser
2012-09-10 17:09 ` Ian Jackson
2012-09-10 17:24 ` Keir Fraser
2012-09-11 10:27 ` Ian Jackson
2012-09-11 10:44 ` Keir Fraser
2012-09-11 10:51 ` Jan Beulich
2012-09-11 10:57 ` Keir Fraser
2012-09-10 16:24 ` David Vrabel
2012-09-10 16:55 ` Keir Fraser [this message]
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=CC73DA0F.3E425%keir.xen@gmail.com \
--to=keir.xen@gmail.com \
--cc=david.vrabel@citrix.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).