From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Jan Beulich <jbeulich@novell.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: irq_guest_eoi_timer interaction with MSI
Date: Tue, 25 Nov 2008 09:38:49 +0000 [thread overview]
Message-ID: <C5517829.1F913%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <492BCAE6.76E4.0078.0@novell.com>
On 25/11/08 08:52, "Jan Beulich" <jbeulich@novell.com> wrote:
>>>> Keir Fraser <keir.fraser@eu.citrix.com> 25.11.08 09:44 >>>
>> ... And lack of 64-bit capability is the only reason not to run 64-bit Xen
>> these days.
>
> Is it, really? That is, are all the save/restore/migrate issues indeed fixed?
> I
> didn't think so, but then again I don't follow closely what happens on the
> tools side...
That's a dom0 vs domU issue. You can run 32-bit dom0 on 64-bit Xen, and that
suffices to avoid Xen's address-space constraints.
-- Keir
next prev parent reply other threads:[~2008-11-25 9:38 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-13 9:22 irq_guest_eoi_timer interaction with MSI Jan Beulich
2008-11-13 9:42 ` Keir Fraser
2008-11-13 11:07 ` Jan Beulich
2008-11-13 11:16 ` Keir Fraser
2008-11-13 11:22 ` Keir Fraser
2008-11-13 14:53 ` Jan Beulich
2008-11-13 15:06 ` Keir Fraser
2008-11-13 15:28 ` Jan Beulich
2008-11-13 16:21 ` Keir Fraser
2008-11-13 16:22 ` Keir Fraser
2008-11-13 16:43 ` Jan Beulich
2008-11-13 16:50 ` Keir Fraser
2008-11-14 9:28 ` Jan Beulich
2008-11-14 9:42 ` Keir Fraser
2008-11-14 13:00 ` Jan Beulich
2008-11-24 16:34 ` Jan Beulich
2008-11-24 17:02 ` Keir Fraser
2008-11-25 8:15 ` Jan Beulich
2008-11-25 8:30 ` Keir Fraser
2008-11-25 8:40 ` Jan Beulich
2008-11-25 8:44 ` Keir Fraser
2008-11-25 8:52 ` Jan Beulich
2008-11-25 9:38 ` Keir Fraser [this message]
2008-11-25 10:12 ` Jan Beulich
2008-11-25 10:47 ` 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=C5517829.1F913%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=jbeulich@novell.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 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.