lkml.org 
[lkml]   [2008]   [Sep]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [RFC 0/4] dynamically allocate arch specific system vectors
    Dean Nelson wrote:
    >
    > sgi-gru driver
    >
    > The GRU is not an actual external device that is connected to an IOAPIC.
    > The gru is a hardware mechanism that is embedded in the node controller
    > (UV hub) that directly connects to the cpu socket. Any cpu (with permission)
    > can do direct loads and stores to the gru. Some of these stores will result
    > in an interrupt being sent back to the cpu that did the store.
    >
    > The interrupt vector used for this interrupt is not in an IOAPIC. Instead
    > it must be loaded into the GRU at boot or driver initialization time.
    >

    Could you clarify there: is this one vector number per CPU, or are you
    issuing a specific vector number and just varying the CPU number?

    -hpa


    \
     
     \ /
      Last update: 2008-09-17 21:23    [W:7.836 / U:0.080 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site