[lkml]   [2007]   [Jan]   [29]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH 0/6] MSI portability cleanups
    Michael Ellerman writes:

    > You can read config space, but it's not clear to me if the HV is allowed
    > to filter it and hide things. It's also possible that the device

    It appears that the HV does not prevent us from reading or writing any
    config space registers for functions that are assigned to us.

    > supports MSI, but for some reason the HV doesn't allow it on that device
    > etc. so you really have to ask the HV if it's enabled. So pci_find_cap()
    > shouldn't crash or anything, but it may lie to you.

    It's possible that the device can do MSI(X), but that using MSI(X)
    requires other platform resources (e.g. interrupt source numbers) and
    there are none free. I believe the platform guarantees a minimum
    number of MSI(X) interrupts per function, but a pci_enable_msix() call
    may not be able to give the driver as many MSI-X interrupts as it is
    requesting even if the function can handle that many.

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2007-01-30 00:31    [W:0.042 / U:0.636 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site