Skip to contentSkip to conversation

PCI: Reduce verbosity of device enable messages

PATCH In review Ammar Qadri 3 participants 6 messages May 7, 2025 – Jul 9, 2025 PCI

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 PCI: Reduce verbosity of device enable messages

Excessive logging of PCIe device enable operations can create significant noise in system logs, especially in environments with a high number of such devices, especially VFs.

High-rate logging can cause log files to rotate too quickly, losing valuable information from other system components.This commit addresses this issue by downgrading the logging level of "enabling device" messages from info to dbg.

---
 drivers/pci/setup-res.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/pci/setup-res.c +1 -1
index c6657cdd06f67..be669ff6ca240 100644
@@ -516,7 +516,7 @@ int pci_enable_resources(struct pci_dev *dev, int mask)
 	}
 
 	if (cmd != old_cmd) {
-		pci_info(dev, "enabling device (%04x -> %04x)\n", old_cmd, cmd);
+		pci_dbg(dev, "enabling device (%04x -> %04x)\n", old_cmd, cmd);
 		pci_write_config_word(dev, PCI_COMMAND, cmd);
 	}
 	return 0;
Signature · 1 line
2.49.0.987.g0cc8ee98dc-goog
#1 lore raw
Quoted 9 lines · Ammar Qadri

Excessive logging of PCIe device enable operations can create significant noise in system logs, especially in environments with a high number of such devices, especially VFs.

High-rate logging can cause log files to rotate too quickly, losing valuable information from other system components.This commit addresses this issue by downgrading the logging level of "enabling device" messages from info to dbg.

While I generally prefer reduced verbosity of the device drivers, demoting an existing log to debug might surprise users. Especially in this case, the message is widely used to identify the enablement of a PCI device. So I don't think it is a good idea to demote it to a debug log.

But I'm surprised that this single message is creating much overhead in the logging. I understand that you might have 100s of VFs in cloud environments, but when a VF is added, a bunch of other messages would also get printed (resource, IRQ, device driver etc...). Or you considered that this message is not that important compared to the rest?

- Mani

Quoted 21 lines
---
 drivers/pci/setup-res.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/pci/setup-res.c +1 -1
index c6657cdd06f67..be669ff6ca240 100644
@@ -516,7 +516,7 @@ int pci_enable_resources(struct pci_dev *dev, int mask)
 	}
 
 	if (cmd != old_cmd) {
-		pci_info(dev, "enabling device (%04x -> %04x)\n", old_cmd, cmd);
+		pci_dbg(dev, "enabling device (%04x -> %04x)\n", old_cmd, cmd);
 		pci_write_config_word(dev, PCI_COMMAND, cmd);
 	}
 	return 0;
Signature · 1 line
2.49.0.987.g0cc8ee98dc-goog
Signature · 1 line
மணிவண்ணன் சதாசிவம்
#2 lore raw

Hi Mani,

The issue we are experiencing is not caused from removing/reattaching the device driver, so the other messages have not been problematic.

The vfio-pci driver is attached to each VF once. Clients in our system call open and close on the vfio-pci driver, respectively, at the start and end of their use,
with fairly short-term tenancy, which ends up triggering these enable messages. This message is proving challenging not only because they are not particularly useful, but because they are causing log files to rotate once every 30 minutes or so, and we lose a lot of other more valuable logging as a consequence. I'm open to other solutions, but in my opinion this preserves the message, without over-engineering and introducing throttling or other behaviour.

Quoted 49 lines · Manivannan Sadhasivam
Quoted 9 lines · Ammar Qadri

Excessive logging of PCIe device enable operations can create significant noise in system logs, especially in environments with a high number of such devices, especially VFs.

High-rate logging can cause log files to rotate too quickly, losing valuable information from other system components.This commit addresses this issue by downgrading the logging level of "enabling device" messages from info to dbg.

While I generally prefer reduced verbosity of the device drivers, demoting an existing log to debug might surprise users. Especially in this case, the message is widely used to identify the enablement of a PCI device. So I don't think it is a good idea to demote it to a debug log.

But I'm surprised that this single message is creating much overhead in the logging. I understand that you might have 100s of VFs in cloud environments, but when a VF is added, a bunch of other messages would also get printed (resource, IRQ, device driver etc...). Or you considered that this message is not that important compared to the rest?

- Mani

Quoted 19 lines
---
 drivers/pci/setup-res.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/pci/setup-res.c +1 -2
index c6657cdd06f67..be669ff6ca240 100644
@@ -516,7 +516,7 @@ int pci_enable_resources(struct pci_dev *dev, int mask)
      }
 
      if (cmd != old_cmd) {
-             pci_info(dev, "enabling device (%04x -> %04x)\n", old_cmd, cmd);
+             pci_dbg(dev, "enabling device (%04x -> %04x)\n", old_cmd, cmd);
              pci_write_config_word(dev, PCI_COMMAND, cmd);
      }
      return 0;
--
Quoted 2 lines

2.49.0.987.g0cc8ee98dc-goog

--
மணிவண்ணன் சதாசிவம்

#3 lore raw
Quoted 6 lines · Ammar Qadri

Hi Mani,

The issue we are experiencing is not caused from removing/reattaching the device driver, so the other messages have not been problematic.

Quoted 10 lines

The vfio-pci driver is attached to each VF once. Clients in our system call open and close on the vfio-pci driver, respectively, at the start and end of their use, with fairly short-term tenancy, which ends up triggering these enable messages. This message is proving challenging not only because they are not particularly useful, but because they are causing log files to rotate once every 30 minutes or so, and we lose a lot of other more valuable logging as a consequence. I'm open to other solutions, but in my opinion this preserves the message, without over-engineering and introducing throttling or other behaviour.

Are there any other messages associated with the open/close? I assume probably not, or you would want to demote those as well.

I did happen to find some value in this particular message just the other day because it showed that a config read was successful after previous ones had failed.

But I agree in general that it's fairly low value and at least the uninterpreted "%04x -> %04x" part is not really user-friendly.

If people think there's enough value in retaining it at KERN_INFO, I suppose there's always the option of carrying an out-of-tree patch to demote it?

Quoted 50 lines · Manivannan Sadhasivam
Quoted 49 lines · Ammar Qadri
Quoted 9 lines

Excessive logging of PCIe device enable operations can create significant noise in system logs, especially in environments with a high number of such devices, especially VFs.

High-rate logging can cause log files to rotate too quickly, losing valuable information from other system components.This commit addresses this issue by downgrading the logging level of "enabling device" messages from info to dbg.

While I generally prefer reduced verbosity of the device drivers, demoting an existing log to debug might surprise users. Especially in this case, the message is widely used to identify the enablement of a PCI device. So I don't think it is a good idea to demote it to a debug log.

But I'm surprised that this single message is creating much overhead in the logging. I understand that you might have 100s of VFs in cloud environments, but when a VF is added, a bunch of other messages would also get printed (resource, IRQ, device driver etc...). Or you considered that this message is not that important compared to the rest?

- Mani

Quoted 19 lines
---
 drivers/pci/setup-res.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/pci/setup-res.c +1 -2
index c6657cdd06f67..be669ff6ca240 100644
@@ -516,7 +516,7 @@ int pci_enable_resources(struct pci_dev *dev, int mask)
      }
 
      if (cmd != old_cmd) {
-             pci_info(dev, "enabling device (%04x -> %04x)\n", old_cmd, cmd);
+             pci_dbg(dev, "enabling device (%04x -> %04x)\n", old_cmd, cmd);
              pci_write_config_word(dev, PCI_COMMAND, cmd);
      }
      return 0;
--
Quoted 2 lines

2.49.0.987.g0cc8ee98dc-goog

--
மணிவண்ணன் சதாசிவம்

#4 lore raw

This is the only message I can see being consistently printed as a result of the open/close of the devices.

I am not opposed to carrying this out of tree at all, but for the sake of exhausting options people would be comfortable with, would you be okay with moving this to dev_dbg, or would you have the same hesitations, Mani (et al)? Or is there some alternative flag-controlled behavior you'd recommend?

Quoted 83 lines · Bjorn Helgaas
Quoted 6 lines · Ammar Qadri

Hi Mani,

The issue we are experiencing is not caused from removing/reattaching the device driver, so the other messages have not been problematic.

Quoted 10 lines

The vfio-pci driver is attached to each VF once. Clients in our system call open and close on the vfio-pci driver, respectively, at the start and end of their use, with fairly short-term tenancy, which ends up triggering these enable messages. This message is proving challenging not only because they are not particularly useful, but because they are causing log files to rotate once every 30 minutes or so, and we lose a lot of other more valuable logging as a consequence. I'm open to other solutions, but in my opinion this preserves the message, without over-engineering and introducing throttling or other behaviour.

Are there any other messages associated with the open/close? I assume probably not, or you would want to demote those as well.

I did happen to find some value in this particular message just the other day because it showed that a config read was successful after previous ones had failed.

But I agree in general that it's fairly low value and at least the uninterpreted "%04x -> %04x" part is not really user-friendly.

If people think there's enough value in retaining it at KERN_INFO, I suppose there's always the option of carrying an out-of-tree patch to demote it?

Quoted 50 lines · Manivannan Sadhasivam
Quoted 49 lines · Ammar Qadri
Quoted 9 lines

Excessive logging of PCIe device enable operations can create significant noise in system logs, especially in environments with a high number of such devices, especially VFs.

High-rate logging can cause log files to rotate too quickly, losing valuable information from other system components.This commit addresses this issue by downgrading the logging level of "enabling device" messages from info to dbg.

While I generally prefer reduced verbosity of the device drivers, demoting an existing log to debug might surprise users. Especially in this case, the message is widely used to identify the enablement of a PCI device. So I don't think it is a good idea to demote it to a debug log.

But I'm surprised that this single message is creating much overhead in the logging. I understand that you might have 100s of VFs in cloud environments, but when a VF is added, a bunch of other messages would also get printed (resource, IRQ, device driver etc...). Or you considered that this message is not that important compared to the rest?

- Mani

Quoted 19 lines
---
 drivers/pci/setup-res.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/pci/setup-res.c +1 -2
index c6657cdd06f67..be669ff6ca240 100644
@@ -516,7 +516,7 @@ int pci_enable_resources(struct pci_dev *dev, int mask)
      }
 
      if (cmd != old_cmd) {
-             pci_info(dev, "enabling device (%04x -> %04x)\n", old_cmd, cmd);
+             pci_dbg(dev, "enabling device (%04x -> %04x)\n", old_cmd, cmd);
              pci_write_config_word(dev, PCI_COMMAND, cmd);
      }
      return 0;
--
Quoted 2 lines

2.49.0.987.g0cc8ee98dc-goog

--
மணிவண்ணன் சதாசிவம்

#5 lore raw
Quoted 8 lines · Ammar Qadri

This is the only message I can see being consistently printed as a result of the open/close of the devices.

I am not opposed to carrying this out of tree at all, but for the sake of exhausting options people would be comfortable with, would you be okay with moving this to dev_dbg, or would you have the same hesitations, Mani (et al)? Or is there some alternative flag-controlled behavior you'd recommend?

pci_dbg() (as you proposed) is just syntactic sugar for dev_dbg(), so they're functionally the same.

Personally I think "enabling device (0000 -> 0002)" is probably not interesting enough to be an 'info' message. Every driver is going to call pci_enable_device() (unless it only uses config space). If it wants to emit a message in its .probe() function it can, and it can include more useful information than whether we're setting the Memory or I/O decoding enable bits.

We already have a similar "enabling bus mastering" message in __pci_set_master() that is already pci_dbg(). So I propose:

- Demoting it to pci_dbg()

- Decoding the bits, e.g., "enabling MEM decoding"

- Adding hints about how to enable pci_dbg() messages to Documentation/admin-guide/kernel-parameters.txt

Quoted 84 lines · Bjorn Helgaas
Quoted 83 lines · Ammar Qadri
Quoted 6 lines

Hi Mani,

The issue we are experiencing is not caused from removing/reattaching the device driver, so the other messages have not been problematic.

Quoted 10 lines

The vfio-pci driver is attached to each VF once. Clients in our system call open and close on the vfio-pci driver, respectively, at the start and end of their use, with fairly short-term tenancy, which ends up triggering these enable messages. This message is proving challenging not only because they are not particularly useful, but because they are causing log files to rotate once every 30 minutes or so, and we lose a lot of other more valuable logging as a consequence. I'm open to other solutions, but in my opinion this preserves the message, without over-engineering and introducing throttling or other behaviour.

Are there any other messages associated with the open/close? I assume probably not, or you would want to demote those as well.

I did happen to find some value in this particular message just the other day because it showed that a config read was successful after previous ones had failed.

But I agree in general that it's fairly low value and at least the uninterpreted "%04x -> %04x" part is not really user-friendly.

If people think there's enough value in retaining it at KERN_INFO, I suppose there's always the option of carrying an out-of-tree patch to demote it?

Quoted 50 lines · Manivannan Sadhasivam
Quoted 49 lines · Ammar Qadri
Quoted 9 lines

Excessive logging of PCIe device enable operations can create significant noise in system logs, especially in environments with a high number of such devices, especially VFs.

High-rate logging can cause log files to rotate too quickly, losing valuable information from other system components.This commit addresses this issue by downgrading the logging level of "enabling device" messages from info to dbg.

While I generally prefer reduced verbosity of the device drivers, demoting an existing log to debug might surprise users. Especially in this case, the message is widely used to identify the enablement of a PCI device. So I don't think it is a good idea to demote it to a debug log.

But I'm surprised that this single message is creating much overhead in the logging. I understand that you might have 100s of VFs in cloud environments, but when a VF is added, a bunch of other messages would also get printed (resource, IRQ, device driver etc...). Or you considered that this message is not that important compared to the rest?

- Mani

Quoted 19 lines
---
 drivers/pci/setup-res.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/pci/setup-res.c +1 -2
index c6657cdd06f67..be669ff6ca240 100644
@@ -516,7 +516,7 @@ int pci_enable_resources(struct pci_dev *dev, int mask)
      }
 
      if (cmd != old_cmd) {
-             pci_info(dev, "enabling device (%04x -> %04x)\n", old_cmd, cmd);
+             pci_dbg(dev, "enabling device (%04x -> %04x)\n", old_cmd, cmd);
              pci_write_config_word(dev, PCI_COMMAND, cmd);
      }
      return 0;
--
Quoted 2 lines

2.49.0.987.g0cc8ee98dc-goog

--
மணிவண்ணன் சதாசிவம்