[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH v5 2/8] xenalyze: increase NR_CPUS to 256

To: Julien Grall <julien.grall@xxxxxxxxxx>
From: Olaf Hering <olaf@xxxxxxxxx>
Date: Thu, 11 Jun 2015 08:12:26 +0200
Cc: Wei Liu <wei.liu2@xxxxxxxxxx>, Ian Campbell <ian.campbell@xxxxxxxxxx>, Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>, George Dunlap <george.dunlap@xxxxxxxxxxxxx>, Ian Jackson <ian.jackson@xxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxx
Delivery-date: Thu, 11 Jun 2015 06:12:43 +0000
List-id: Xen developer discussion <xen-devel.lists.xen.org>

On Wed, Jun 10, Julien Grall wrote:

> There is also a variable MAX_CPUS defined to 256. which is used every.

You are right, while forwarding an old patch (from memory) I changed the
wrong place. MAX_CPUS is already at 256 so no change is strictly
neccessary.

I suggest to drop that patch from this series while applying.
Thanks for the review.

Olaf

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel

Follow-Ups:
- Re: [Xen-devel] [PATCH v5 2/8] xenalyze: increase NR_CPUS to 256
  - From: Julien Grall

References:
- [Xen-devel] [PATCH v5 0/8] add xenalyze to staging
  - From: Olaf Hering
- [Xen-devel] [PATCH v5 2/8] xenalyze: increase NR_CPUS to 256
  - From: Olaf Hering
- Re: [Xen-devel] [PATCH v5 2/8] xenalyze: increase NR_CPUS to 256
  - From: Julien Grall

Prev by Date: Re: [Xen-devel] [PATCH] Modified RTDS scheduler to use an event-driven model instead of polling.
Next by Date: Re: [Xen-devel] Alternate p2m design specification
Previous by thread: Re: [Xen-devel] [PATCH v5 2/8] xenalyze: increase NR_CPUS to 256
Next by thread: Re: [Xen-devel] [PATCH v5 2/8] xenalyze: increase NR_CPUS to 256
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.