[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] [PATCH RFC v1 3/4] libxl for rt scheduler
- To: Ian Campbell <Ian.Campbell@xxxxxxxxxx>
- From: Meng Xu <xumengpanda@xxxxxxxxx>
- Date: Fri, 18 Jul 2014 07:05:13 -0400
- Cc: "xisisu@xxxxxxxxx" <xisisu@xxxxxxxxx>, "stefano.stabellini@xxxxxxxxxxxxx" <stefano.stabellini@xxxxxxxxxxxxx>, "george.dunlap@xxxxxxxxxxxxx" <george.dunlap@xxxxxxxxxxxxx>, "dario.faggioli@xxxxxxxxxx" <dario.faggioli@xxxxxxxxxx>, "ian.jackson@xxxxxxxxxxxxx" <ian.jackson@xxxxxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxx>, Meng Xu <mengxu@xxxxxxxxxxxxx>, "lichong659@xxxxxxxxx" <lichong659@xxxxxxxxx>, "dgolomb@xxxxxxxxxxxxxx" <dgolomb@xxxxxxxxxxxxxx>
- Delivery-date: Fri, 18 Jul 2014 11:05:19 +0000
- List-id: Xen developer discussion <xen-devel.lists.xen.org>
Hi Ian,
Ian Campbell <Ian.Campbell@xxxxxxxxxx>ä2014å7æ17æææååéï
On Fri, 2014-07-11 at 00:49 -0400, Meng Xu wrote:
> +/* Consistent with XEN_LEGACY_MAX_VCPUS xen/arch-x86/xen.h*/
> +#define LIBXL_XEN_LEGACY_MAX_VCPUS Â Â Â Â Â Â Â Â Â32
As the name suggests this limit is legacy. Modern Xen and modern guests
can support considerably more VCPUs than this.
You need to base your interface on a dynamically sized/allocated array.
Perhaps this needs to be carried down all the way to the domctl
interface and into Xen, I haven't looked.
Yes. You are right! I'm going to dynamically allocate the array, instead of use the LIBXL_XEN_LEGACY_MAX_VCPUS, in the next version. Â
Thanks,
Meng Â
--
-----------
Meng Xu
PhD Student in Computer and Information Science
University of Pennsylvania
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel
|
