Re: [PATCH] tracing: Expose CPU physical addresses (resource values) for PCI devices

2016-06-20 Thread Steven Rostedt
On Sat, 18 Jun 2016 08:23:23 +1000 Benjamin Herrenschmidt wrote: > On Fri, 2016-06-17 at 17:59 -0400, Steven Rostedt wrote: > > Sorry for the late reply, this patch got pushed down in my INBOX. > > > > Could I get someone from PPC to review this patch, just to be safe? > > The patch makes sen

Re: [PATCH] tracing: Expose CPU physical addresses (resource values) for PCI devices

2016-06-17 Thread Benjamin Herrenschmidt
On Fri, 2016-06-17 at 17:59 -0400, Steven Rostedt wrote: > Sorry for the late reply, this patch got pushed down in my INBOX. > > Could I get someone from PPC to review this patch, just to be safe? The patch makes sense, I can try getting somebody onto porting mmiotrace one of these days. Cheers,

Re: [PATCH] tracing: Expose CPU physical addresses (resource values) for PCI devices

2016-06-17 Thread Steven Rostedt
Sorry for the late reply, this patch got pushed down in my INBOX. Could I get someone from PPC to review this patch, just to be safe? Thanks! -- Steve On Wed, 11 May 2016 14:06:57 -0500 Bjorn Helgaas wrote: > Previously, mmio_print_pcidev() put "user" addresses in the trace buffer. > On mo

[PATCH] tracing: Expose CPU physical addresses (resource values) for PCI devices

2016-05-11 Thread Bjorn Helgaas
Previously, mmio_print_pcidev() put "user" addresses in the trace buffer. On most architectures, these are the same as CPU physical addresses, but on microblaze, mips, powerpc, and sparc, they may be something else, typically a raw BAR value (a bus address as opposed to a CPU address). Always expo