From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Christian Tramnitz <chris.ace@gmx.net>
Cc: xen-devel@lists.xensource.com, xen-users@lists.xensource.com
Subject: Re: [Xen-devel] Re: PROPOSAL: Remove 32-bit x86 host support in 4.2 development branch
Date: Mon, 21 Mar 2011 10:58:45 +0000 [thread overview]
Message-ID: <20110321105845.6b945cc0@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <im71am$cru$1@dough.gmane.org>
> superseded by N4xx/N5xx (supporting x64) in 2009 or Atom Z-series
> (targeted at MIDs).
And found in systems like the original Dell mini-10, which I've never
tried with Xen but does handle kvm quite happily.
prev parent reply other threads:[~2011-03-21 10:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-17 14:21 PROPOSAL: Remove 32-bit x86 host support in 4.2 development branch Keir Fraser
2011-03-17 17:11 ` Ian Jackson
2011-03-17 17:23 ` Keir Fraser
2011-03-17 17:25 ` Ian Jackson
2011-03-21 8:13 ` Christian Tramnitz
2011-03-21 10:58 ` Alan Cox [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=20110321105845.6b945cc0@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=chris.ace@gmx.net \
--cc=xen-devel@lists.xensource.com \
--cc=xen-users@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).