From mboxrd@z Thu Jan 1 00:00:00 1970 From: Robert VanVossen Subject: Re: [PATCH 3/4] sched/arinc653: Remove MAX_VIRT_CPUS bounds check Date: Tue, 20 Jan 2015 09:20:56 -0500 Message-ID: <54BE6448.70502@dornerworks.com> References: <1421666496-10676-1-git-send-email-andrew.cooper3@citrix.com> <1421666496-10676-4-git-send-email-andrew.cooper3@citrix.com> <54BE3D290200007800056E41@mail.emea.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <54BE3D290200007800056E41@mail.emea.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Jan Beulich , Andrew Cooper Cc: Keir Fraser , Nathan Studer , Xen-devel List-Id: xen-devel@lists.xenproject.org On 1/20/2015 5:34 AM, Jan Beulich wrote: >>>> On 19.01.15 at 12:21, wrote: >> The arinc653 interface is capable of specifying a domain in the schedule >> (from >> the toolstack) before the domain itself exists, or is present in the cpupool >> (The domain is identified by UUID rather than domid). As a result, the >> schedule can't be validated at this point. >> >> The vcpu_id from userspace is only ever used to compare against a list of >> real >> vcpus available to the scheduler, which prevents ill-specified vcpus from >> actually being scheduled. >> >> Remove the MAX_VIRT_CPUS test, as it is not an appropriate bound for >> vcpu_id. >> >> Signed-off-by: Andrew Cooper > > Reviewed-by: Jan Beulich > Acked-by Robert VanVossen