xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Keir Fraser <keir.xen@gmail.com>
To: xen-devel@lists.xen.org
Cc: Ian Jackson <Ian.Jackson@eu.citrix.com>
Subject: Re: [ANNOUNCE] Xen x86 32-bit hypervisor end of life after 4.2
Date: Mon, 10 Sep 2012 15:00:01 +0100	[thread overview]
Message-ID: <CC73B0F1.3E3CC%keir.xen@gmail.com> (raw)
In-Reply-To: <CC7237F3.3E2CD%keir.xen@gmail.com>

On 09/09/2012 12:11, "Keir Fraser" <keir.xen@gmail.com> 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.

Ian,

Please can you remove x86_32 from the automated tests for xen-unstable?

 Thanks,
 Keir

> 32-bit x86 will continue to be maintained and supported (insofar as it has
> been recently) in the supported stable branches: 3.4, 4.1, and 4.2.
> 
> Furthermore, 32-bit guests (including 32-bit PV guests) will continue to be
> supported on the 64-bit hypervisor, as they always have been.
> 
>  Regards,
>  Keir & The Xen Team
> 
> 

  reply	other threads:[~2012-09-10 14:00 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 [this message]
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

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=CC73B0F1.3E3CC%keir.xen@gmail.com \
    --to=keir.xen@gmail.com \
    --cc=Ian.Jackson@eu.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).