| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| |
|
|
|
| |
The PCISIG recently added the Enhanced Allocation Capability. Decode
it in lspci.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The SlotPowerLimit in the Slot Capability indicates how much power the slot
can supply to a downstream device. A Root Port or Switch Downstream Port
communicates the limit via a Set_Slot_Power_Limit Message on the link. The
component on the other end of the link copies the limit from the message to
the Captured Slot Power Limit in its Device Capability [see PCIe r3.0, sec
2.2.8.5].
The Captured SlotPowerLimit is relevant for all devices on the downstream
end of a Link. This includes Endpoints and Bridges as well as
Switch Upstream Ports.
Decode the DevCap Captured SlotPowerLimit for Endpoints and Bridges as well
as Switch Upstream Ports.
Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Based on patch from
https://bugs.gentoo.org/show_bug.cgi?id=425022
|
| |
|
|
|
| |
Previously, lspci always asked for all attributes, even in terse
mode where most of them are not shown.
|
| |
|
|
|
|
|
|
| |
Ameya Palande reported that with some kernels, reads of such
attributes fail on some hardware. He suggested to ignore read
failures completely, but I decided to turn the errors into
warnings in such cases. At least, the user will know that something
fishy is going on.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
The numa_node field was moved to the end of the public part of
struct pci_dev. As usually, it has to be requested using the
PCI_FILL_NUMA_NODE and pci_fill_info() is versioned.
|
| | |
|
| |
|
|
| |
They are also printed in "-vv" and "-nv" modes now.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
In multi-socket systems, it's useful to see which node a particular
PCI device belongs to. Linux provides this information through sysfs,
but some users don't like poking through sysfs themselves to find it,
and it's pretty straightforward to report it in lspci.
I should note that when there is no NUMA node for a particular device,
Linux reports -1. I've chosen to continue that convention in pciutils,
and simply omit the information if the device does not belong to a NUMA
node (eg on single-socket systems, or devices which are not preferentially
attached to a particular node, like Nehalem-based systems).
|
| |
|
|
| |
Thanks to Robert Urban for pointing it out.
|
| |
|
|
|
|
|
| |
This seems to be a copy&paste error in both directions of the
compat translation.
Signed-off-by: Lucas Stach <dev@lynxeye.de>
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
The support code for libc5 breaks building on linux i386 with
other libcs that don't define __GLIBC__.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
virtio uses vendor-specific capabilities to specify the location of
the virtio register ranges. The specification can be found here:
http://docs.oasis-open.org/virtio/virtio/v1.0/cs01/virtio-v1.0-cs01.html#x1-690004
This patch adds support for decoding these capabilities to lspci.
Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Signed-off-by: Tomáš Chvátal <tchvatal@suse.cz>
---
lib/names-cache.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/lib/names-cache.c b/lib/names-cache.c
index 90a6454..c97ea30 100644
--- a/lib/names-cache.c
+++ b/lib/names-cache.c
@@ -39,7 +39,8 @@ static char *get_cache_name(struct pci_access *a)
buf = pci_malloc(a, strlen(pw->pw_dir) + strlen(name+1) + 1);
sprintf(buf, "%s%s", pw->pw_dir, name+1);
pci_set_param_internal(a, "net.cache_name", buf, 0);
- return buf;
+ pci_mfree(buf);
+ return pci_get_param(a, "net.cache_name");
}
int
--
2.1.3
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
This is tricky, because we have to translate between old and new
format of struct pci_filter. At least, I added several RFU fields
so this hopefully won't have to happen again soon.
|
| |
|
|
|
|
|
|
|
|
| |
Extend the 'filter by device ID' functionality to allow optional
specification of a device ID. For example, to list all USB controllers
in the system made by Intel, specify:
lspci -d 8086::0c03
Signed-off-by: Matthew Wilcox <matthew.r.wilcox@intel.com>
|
| | |
|
| |
|
|
|
|
|
|
|
| |
We do not call .IX as it's not defined in mandoc.
Ellipsis at the end of line is protected by \&.
Inspired by Debian patches for the following bugs:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674708
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675087
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
HWDB is now handled in a way very similar to the DNS resolver.
The interface lives in a separate source file (lib/names-hwdb.c),
results of lookups are cached. Use of HWDB can be disabled either
by passing PCI_LOOKUP_NO_HWDB or by setting the hwdb.disabled
configuration parameter.
Also, there should be no more leaks of libudev's structures.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This lets you select hwdb support at compile time.
hwdb is an efficient hardware database shipped with recent versions of udev. It contains
among other sources pci.ids so querying hwdb rather than reading pci.ids directly should give
the same result.
Ideally Linux distros using udev could stop shipping pci.ids, but use hwdb as the only source
of this information, which this patch allows.
Cc: Martin Mares <mj@ucw.cz>
|
| | |
|
| | |
|
| |
|
|
|
| |
The previous implementation handled labels differently from all
other device properties, which was illogical.
|
| | |
|
