[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [RFC PATCH 01/10] configure: factor out list of support
From: |
Stefano Stabellini |
Subject: |
Re: [Qemu-devel] [RFC PATCH 01/10] configure: factor out list of supported Xen/KVM targets |
Date: |
Mon, 17 Sep 2012 19:21:14 +0100 |
User-agent: |
Alpine 2.02 (DEB 1266 2009-07-14) |
On Mon, 17 Sep 2012, Paolo Bonzini wrote:
> Il 17/09/2012 19:02, Peter Maydell ha scritto:
> > If Xen requires 64 bit physaddrs it should probably just be asserting
> > this here, not randomly changing target_phys_bits. In fact all the
> > supported Xen target archs already have 64 bit physaddrs, so it's
> > harmless. But if there ever were a target Xen arch which didn't support
> > 64 bit phys addrs then the right approach would be to convert it to
> > do so regardless of whether we were using Xen or not.
>
> No, Xen does not require 64-bit physaddrs, but it supports them even if
> you build it for 32-bit. Memory is accessed through a "hole" (the
> mapcache) provided by the hypervisor, so that a 32-bit QEMU address
> space is enough to run 64-bit guests. At least that's my understanding.
Xen requires 64 bit physaddrs because no matter what the specified arch
of the host or the guest at configure time is, the guest could still be
64 bit. In other words: the arch of the guest and the arch of the host
are irrelevant on Xen and physaddrs should always be 64 bit.
[Qemu-devel] [RFC PATCH 08/10] configure: add --disable-tcg configure option, Paolo Bonzini, 2012/09/17
[Qemu-devel] [RFC PATCH 05/10] exec: small adjustments for TCG separation, Paolo Bonzini, 2012/09/17
[Qemu-devel] [RFC PATCH 06/10] monitor: disable info jit if !TCG, Paolo Bonzini, 2012/09/17
[Qemu-devel] [RFC PATCH 09/10] i386: move TCG functions out of helper.o, non-TCG functions to cpu.o, Paolo Bonzini, 2012/09/17