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

[Xen-changelog] [xen master] xen: sched: refactor the ASSERTs around vcpu_deassing()



commit 8d54a6adf42a89350f746000f07ed3f4656ceed2
Author:     Dario Faggioli <dfaggioli@xxxxxxxx>
AuthorDate: Mon Aug 5 11:50:57 2019 +0100
Commit:     George Dunlap <george.dunlap@xxxxxxxxxx>
CommitDate: Mon Aug 5 11:50:57 2019 +0100

    xen: sched: refactor the ASSERTs around vcpu_deassing()
    
    It is all the time that we call vcpu_deassing() that the vcpu _must_ be
    assigned to a pCPU, and hence that such pCPU can't be free.
    
    Therefore, move the ASSERT-s which check for these properties in that
    function, where they belong better.
    
    Signed-off-by: Dario Faggioli <dfaggioli@xxxxxxxx>
    Reviewed-by: George Dunlap <george.dunlap@xxxxxxxxx>
    Message-Id: <156412236781.2385.9110155201477198899.stgit@Palanthas>
---
 xen/common/sched_null.c | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/xen/common/sched_null.c b/xen/common/sched_null.c
index 2edac234a5..26c6f0f129 100644
--- a/xen/common/sched_null.c
+++ b/xen/common/sched_null.c
@@ -368,6 +368,8 @@ static bool vcpu_deassign(struct null_private *prv, struct 
vcpu *v)
     struct null_vcpu *wvc;
 
     ASSERT(list_empty(&null_vcpu(v)->waitq_elem));
+    ASSERT(per_cpu(npc, v->processor).vcpu == v);
+    ASSERT(!cpumask_test_cpu(v->processor, &prv->cpus_free));
 
     per_cpu(npc, cpu).vcpu = NULL;
     cpumask_set_cpu(cpu, &prv->cpus_free);
@@ -529,9 +531,6 @@ static void null_vcpu_remove(const struct scheduler *ops, 
struct vcpu *v)
         goto out;
     }
 
-    ASSERT(per_cpu(npc, v->processor).vcpu == v);
-    ASSERT(!cpumask_test_cpu(v->processor, &prv->cpus_free));
-
     vcpu_deassign(prv, v);
 
  out:
--
generated by git-patchbot for /home/xen/git/xen.git#master

_______________________________________________
Xen-changelog mailing list
Xen-changelog@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/xen-changelog

 


Rackspace

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