[lkml]   [2008]   [Nov]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH] sparse_irq aka dyn_irq v13
    H. Peter Anvin wrote:
    > Yinghai Lu wrote:
    >> H. Peter Anvin wrote:
    >>> It would, however, be a good idea if IOAPICs had their numbers assigned
    >>> at detection time, as opposed to when the interrupt is registered, thus
    >>> making it a stable number for a single boot, at least. The same is
    >>> probably true for MSI(-X); we could assign it a range of numbers when
    >>> the device is enumerated (as opposed to when a driver is activated), but
    >>> I don't know to what extent that is likely to cause more troubles than
    >>> it solves.
    >> how to find the range for MSIX, one device/func may need a lot. for example, niu driver could use 20 MSI-X for one port. (one dev/func)
    >> some could use 256. we only know that when driver is loaded.
    >> So as Eric said, just try to use 12bits (4k range) for them.
    > You can know how many vectors are exported in generic code. However,
    > using 4k per should be fine.

    so we have one list to map domain/bus/dev/func to bits [31,12] in irq ?


     \ /
      Last update: 2008-11-17 02:01    [W:0.026 / U:68.732 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site