Skip to content
Snippets Groups Projects
  • Dave Airlie's avatar
    3448a19d
    vgaarb: use bridges to control VGA routing where possible. · 3448a19d
    Dave Airlie authored
    
    So in a lot of modern systems, a GPU will always be below a parent bridge that won't share with any other GPUs. This means VGA arbitration on those GPUs can be controlled by using the bridge routing instead of io/mem decodes.
    
    The problem is locating which GPUs share which upstream bridges. This patch attempts to identify all the GPUs which can be controlled via bridges, and ones that can't. This patch endeavours to work out the bridge sharing semantics.
    
    When disabling GPUs via a bridge, it doesn't do irq callbacks or touch the io/mem decodes for the gpu.
    
    Signed-off-by: default avatarDave Airlie <airlied@redhat.com>
    3448a19d
    History
    vgaarb: use bridges to control VGA routing where possible.
    Dave Airlie authored
    
    So in a lot of modern systems, a GPU will always be below a parent bridge that won't share with any other GPUs. This means VGA arbitration on those GPUs can be controlled by using the bridge routing instead of io/mem decodes.
    
    The problem is locating which GPUs share which upstream bridges. This patch attempts to identify all the GPUs which can be controlled via bridges, and ones that can't. This patch endeavours to work out the bridge sharing semantics.
    
    When disabling GPUs via a bridge, it doesn't do irq callbacks or touch the io/mem decodes for the gpu.
    
    Signed-off-by: default avatarDave Airlie <airlied@redhat.com>