This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] Re: [PATCH 0/5] Enable QEMU to handle more than 2GB with Xen

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Re: [PATCH 0/5] Enable QEMU to handle more than 2GB with Xen.
From: jiageng_yu <yujiageng734@xxxxxxxxx>
Date: Fri, 22 Jul 2011 00:20:05 -0700 (PDT)
Delivery-date: Fri, 22 Jul 2011 00:22:40 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1310740376-13323-1-git-send-email-anthony.perard@xxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <1310740376-13323-1-git-send-email-anthony.perard@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hi Anthony,

   I have questions on CONFIG_XEN_BACKEND in the patches.

   Where to define the CONFIG_XEN_BACKEND option? Due to lacking of
CONFIG_XEN_BACKEND option, the xen_enabled() returns 0 in the phase of
initial qemu machine. How to avoid this problem?

   I am working on qemu-dm-v15 branch, and I wonder if I could apply these
patches without switching branches.


Jiageng Yu.

View this message in context: 
Sent from the Xen - Dev mailing list archive at Nabble.com.

Xen-devel mailing list