PM / core: Use dev_printk() and symbols in suspend/resume diagnostics
authorBjorn Helgaas <bhelgaas@google.com>
Thu, 26 Apr 2018 21:36:41 +0000 (16:36 -0500)
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>
Thu, 10 May 2018 09:31:45 +0000 (11:31 +0200)
commit7f817ba942940df382de085f9b830f77411562f2
tree6b36b99a8fa24847565fc69d716b9f59edb08166
parent143711f0110637239f045a179e726b137b7caf59
PM / core: Use dev_printk() and symbols in suspend/resume diagnostics

When we print diagnostic messages about suspend/resume, we have a device
pointer, so use dev_printk() to match other device-related things.  Add the
function name, similar to initcall_debug output.  E.g.,

  - calling  0000:01:00.0+ @ 998, parent: 0000:00:1c.0
  + pci 0000:01:00.0: calling <something> @ 998, parent: 0000:00:1c.0

I wondered if this would break scripts/bootgraph.pl, but I don't think it
will because bootgraph.pl doesn't add any timing information to $start{}
after it sees "Write protecting the" or "Freeing unused kernel memory".

Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
drivers/base/power/main.c