Skip to content
  • Paolo Bonzini's avatar
    88691b37
    blockjob: separate monitor and blockjob APIs · 88691b37
    Paolo Bonzini authored
    
    
    We have two different headers for block job operations, blockjob.h
    and blockjob_int.h.  The former contains APIs called by the monitor,
    the latter contains APIs called by the block job drivers and the
    block layer itself.
    
    Keep the two APIs separate in the blockjob.c file too.  This will
    be useful when transitioning away from the AioContext lock, because
    there will be locking policies for the two categories, too---the
    monitor will have to call new block_job_lock/unlock APIs, while blockjob
    APIs will take care of this for the users.
    
    Reviewed-by: default avatarStefan Hajnoczi <stefanha@redhat.com>
    Signed-off-by: default avatarPaolo Bonzini <pbonzini@redhat.com>
    Message-id: 20170508141310.8674-6-pbonzini@redhat.com
    Signed-off-by: default avatarJeff Cody <jcody@redhat.com>
    88691b37
    blockjob: separate monitor and blockjob APIs
    Paolo Bonzini authored
    
    
    We have two different headers for block job operations, blockjob.h
    and blockjob_int.h.  The former contains APIs called by the monitor,
    the latter contains APIs called by the block job drivers and the
    block layer itself.
    
    Keep the two APIs separate in the blockjob.c file too.  This will
    be useful when transitioning away from the AioContext lock, because
    there will be locking policies for the two categories, too---the
    monitor will have to call new block_job_lock/unlock APIs, while blockjob
    APIs will take care of this for the users.
    
    Reviewed-by: default avatarStefan Hajnoczi <stefanha@redhat.com>
    Signed-off-by: default avatarPaolo Bonzini <pbonzini@redhat.com>
    Message-id: 20170508141310.8674-6-pbonzini@redhat.com
    Signed-off-by: default avatarJeff Cody <jcody@redhat.com>
Loading