ef27a04299
- Simplify the amount of work that has be done for each architecture by pushing more of the truly MI code down into the PCI bus driver. - Don't bind MSI-X indicies to IRQs so that we can allow a driver to map multiple MSI-X messages into a single IRQ when handling a message shortage. The changes include: - Add a new pcib_if method: PCIB_MAP_MSI() which is called by the PCI bus to calculate the address and data values for a given MSI/MSI-X IRQ. The x86 nexus drivers map this into a call to a new 'msi_map()' function in msi.c that does the mapping. - Retire the pcib_if method PCIB_REMAP_MSIX() and remove the 'index' parameter from PCIB_ALLOC_MSIX(). MD code no longer has any knowledge of the MSI-X index for a given MSI-X IRQ. - The PCI bus driver now stores more MSI-X state in a child's ivars. Specifically, it now stores an array of IRQs (called "message vectors" in the code) that have associated address and data values, and a small virtual version of the MSI-X table that specifies the message vector that a given MSI-X table entry uses. Sparse mappings are permitted in the virtual table. - The PCI bus driver now configures the MSI and MSI-X address/data registers directly via custom bus_setup_intr() and bus_teardown_intr() methods. pci_setup_intr() invokes PCIB_MAP_MSI() to determine the address and data values for a given message as needed. The MD code no longer has to call back down into the PCI bus code to set these values from the nexus' bus_setup_intr() handler. - The PCI bus code provides a callout (pci_remap_msi_irq()) that the MD code can call to force the PCI bus to re-invoke PCIB_MAP_MSI() to get new values of the address and data fields for a given IRQ. The x86 MSI code uses this when an MSI IRQ is moved to a different CPU, requiring a new value of the 'address' field. - The x86 MSI psuedo-driver loses a lot of code, and in fact the separate MSI/MSI-X pseudo-PICs are collapsed down into a single MSI PIC driver since the only remaining diff between the two is a substring in a bootverbose printf. - The PCI bus driver will now restore MSI-X state (including programming entries in the MSI-X table) on device resume. - The interface for pci_remap_msix() has changed. Instead of accepting indices for the allocated vectors, it accepts a mini-virtual table (with a new length parameter). This table is an array of u_ints, where each value specifies which allocated message vector to use for the corresponding MSI-X message. A vector of 0 forces a message to not have an associated IRQ. The device may choose to only use some of the IRQs assigned, in which case the unused IRQs must be at the "end" and will be released back to the system. This allows a driver to use the same remap table for different shortage values. For example, if a driver wants 4 messages, it can use the same remap table (which only uses the first two messages) for the cases when it only gets 2 or 3 messages and in the latter case the PCI bus will release the 3rd IRQ back to the system. MFC after: 1 month
147 lines
3.8 KiB
Objective-C
147 lines
3.8 KiB
Objective-C
#-
|
|
# Copyright (c) 2000 Doug Rabson
|
|
# All rights reserved.
|
|
#
|
|
# Redistribution and use in source and binary forms, with or without
|
|
# modification, are permitted provided that the following conditions
|
|
# are met:
|
|
# 1. Redistributions of source code must retain the above copyright
|
|
# notice, this list of conditions and the following disclaimer.
|
|
# 2. Redistributions in binary form must reproduce the above copyright
|
|
# notice, this list of conditions and the following disclaimer in the
|
|
# documentation and/or other materials provided with the distribution.
|
|
#
|
|
# THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
|
|
# ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
|
|
# IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
|
|
# ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
|
|
# FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
|
|
# DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
|
|
# OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
|
|
# HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
|
|
# LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
|
|
# OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
|
|
# SUCH DAMAGE.
|
|
#
|
|
# $FreeBSD$
|
|
#
|
|
|
|
#include <sys/bus.h>
|
|
#include <dev/pci/pcivar.h>
|
|
|
|
INTERFACE pcib;
|
|
|
|
CODE {
|
|
static int
|
|
null_route_interrupt(device_t pcib, device_t dev, int pin)
|
|
{
|
|
return (PCI_INVALID_IRQ);
|
|
}
|
|
};
|
|
|
|
#
|
|
# Return the number of slots on the attached PCI bus.
|
|
#
|
|
METHOD int maxslots {
|
|
device_t dev;
|
|
};
|
|
|
|
#
|
|
# Read configuration space on the PCI bus. The bus, slot and func
|
|
# arguments determine the device which is being read and the reg
|
|
# argument is a byte offset into configuration space for that
|
|
# device. The width argument (which should be 1, 2 or 4) specifies how
|
|
# many byte of configuration space to read from that offset.
|
|
#
|
|
METHOD u_int32_t read_config {
|
|
device_t dev;
|
|
u_int bus;
|
|
u_int slot;
|
|
u_int func;
|
|
u_int reg;
|
|
int width;
|
|
};
|
|
|
|
#
|
|
# Write configuration space on the PCI bus. The bus, slot and func
|
|
# arguments determine the device which is being written and the reg
|
|
# argument is a byte offset into configuration space for that
|
|
# device. The value field is written to the configuration space, with
|
|
# the number of bytes written depending on the width argument.
|
|
#
|
|
METHOD void write_config {
|
|
device_t dev;
|
|
u_int bus;
|
|
u_int slot;
|
|
u_int func;
|
|
u_int reg;
|
|
u_int32_t value;
|
|
int width;
|
|
};
|
|
|
|
#
|
|
# Route an interrupt. Returns a value suitable for stuffing into
|
|
# a device's interrupt register.
|
|
#
|
|
METHOD int route_interrupt {
|
|
device_t pcib;
|
|
device_t dev;
|
|
int pin;
|
|
} DEFAULT null_route_interrupt;
|
|
|
|
#
|
|
# Allocate 'count' MSI messsages mapped onto 'count' IRQs. 'irq' points
|
|
# to an array of at least 'count' ints. The max number of messages this
|
|
# device supports is included so that the MD code can take that into
|
|
# account when assigning resources so that the proper number of low bits
|
|
# are clear in the resulting message data value.
|
|
#
|
|
METHOD int alloc_msi {
|
|
device_t pcib;
|
|
device_t dev;
|
|
int count;
|
|
int maxcount;
|
|
int *irqs;
|
|
};
|
|
|
|
#
|
|
# Release 'count' MSI messages mapped onto 'count' IRQs stored in the
|
|
# array pointed to by 'irqs'.
|
|
#
|
|
METHOD int release_msi {
|
|
device_t pcib;
|
|
device_t dev;
|
|
int count;
|
|
int *irqs;
|
|
};
|
|
|
|
#
|
|
# Allocate a single MSI-X message mapped onto '*irq'.
|
|
#
|
|
METHOD int alloc_msix {
|
|
device_t pcib;
|
|
device_t dev;
|
|
int *irq;
|
|
};
|
|
|
|
#
|
|
# Release a single MSI-X message mapped onto 'irq'.
|
|
#
|
|
METHOD int release_msix {
|
|
device_t pcib;
|
|
device_t dev;
|
|
int irq;
|
|
};
|
|
|
|
#
|
|
# Determine the MSI/MSI-X message address and data for 'irq'. The address
|
|
# is returned in '*addr', and the data in '*data'.
|
|
#
|
|
METHOD int map_msi {
|
|
device_t pcib;
|
|
device_t dev;
|
|
int irq;
|
|
uint64_t *addr;
|
|
uint32_t *data;
|
|
};
|