From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Keir Fraser <keir@xen.org>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Jan Beulich <JBeulich@suse.com>
Subject: Re: [PATCH] x86-64: don't use xmalloc_array() for allocation of the (per-CPU) IDTs
Date: Thu, 13 Oct 2011 14:36:31 -0400 [thread overview]
Message-ID: <20111013183631.GJ15499@phenom.oracle.com> (raw)
In-Reply-To: <CABC5CBD.32774%keir@xen.org>
On Thu, Oct 13, 2011 at 09:15:41AM +0100, Keir Fraser wrote:
> On 13/10/2011 08:55, "Jan Beulich" <JBeulich@suse.com> wrote:
>
> >>>> On 13.10.11 at 09:50, Keir Fraser <keir@xen.org> wrote:
> >> Finally, I'm not sure about more x86-64 code movement: I'd like to kill
> >> x86-32 entirely really.
> >
> > I know, but you got pushed back each time you tried...
>
> I think we're stuck with it for 4.2. Will try again when we open development
> for 4.3. The argument last time was the low-powered Atoms, used in low-end
> netbooks; but there's no evidence that anyone is using Xen on such
> platforms. I can't imagine it would be very worthwhile.
I've actually been using Xen 4.1.1 on them. But the Atom I've is 64-bit capable.
next prev parent reply other threads:[~2011-10-13 18:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-13 7:21 [PATCH] x86-64: don't use xmalloc_array() for allocation of the (per-CPU) IDTs Jan Beulich
2011-10-13 7:50 ` Keir Fraser
2011-10-13 7:55 ` Jan Beulich
2011-10-13 8:15 ` Keir Fraser
2011-10-13 18:36 ` Konrad Rzeszutek Wilk [this message]
2011-10-13 9:34 ` Keir Fraser
2011-10-13 12:14 ` Jan Beulich
2011-10-13 14:44 ` Keir Fraser
2011-10-13 15:16 ` Jan Beulich
2011-10-13 15:23 ` 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=20111013183631.GJ15499@phenom.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=JBeulich@suse.com \
--cc=keir@xen.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.