From: Shuai Xue <xueshuai@linux.alibaba.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: lukas@wunner.de, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-edac@vger.kernel.org,
linux-trace-kernel@vger.kernel.org, helgaas@kernel.org,
bhelgaas@google.com, tony.luck@intel.com, bp@alien8.de,
mhiramat@kernel.org, mathieu.desnoyers@efficios.com,
oleg@redhat.com, naveen@kernel.org, davem@davemloft.net,
anil.s.keshavamurthy@intel.com, mark.rutland@arm.com,
peterz@infradead.org, tianruidong@linux.alibaba.com
Subject: Re: [PATCH v7] PCI: hotplug: Add a generic RAS tracepoint for hotplug event
Date: Thu, 8 May 2025 09:24:32 +0800 [thread overview]
Message-ID: <f88d35e2-c739-4432-a7fa-35c8a2dd2e9a@linux.alibaba.com> (raw)
In-Reply-To: <20250507113640.0b27d95f@gandalf.local.home>
在 2025/5/7 23:36, Steven Rostedt 写道:
> On Wed, 7 May 2025 09:15:35 +0800
> Shuai Xue <xueshuai@linux.alibaba.com> wrote:
>
>> +#endif /* _TRACE_HW_EVENT_PCI_HP_H */
>> +
>> +#undef TRACE_INCLUDE_PATH
>> +#define TRACE_INCLUDE_PATH ../../drivers/pci/hotplug
>
> Note, this is not always safe to do. If "drivers", "pci" or "hotplug" ever
> become a macro, the path will also be updated, and this will fail to build.
>
>> +#undef TRACE_INCLUDE_FILE
>> +#define TRACE_INCLUDE_FILE trace
>> +
>> +/* This part must be outside protection */
>> +#include <trace/define_trace.h>
>> diff --git a/include/uapi/linux/pci.h b/include/uapi/linux/pci.h
>
> The safer way to do this is to have:
>
> In drivers/pci/hotplug/Makefile:
>
> CFLAGS_pciehp_ctrl.o := -I$(src)
>
> And replace the TRACE_INCLUDE_PATH to:
>
> #define TRACE_INCLUDE_PATH .
>
> -- Steve
Got it. Will fix it in next version.
Thanks.
Shuai
prev parent reply other threads:[~2025-05-08 1:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-07 1:15 [PATCH v7] PCI: hotplug: Add a generic RAS tracepoint for hotplug event Shuai Xue
2025-05-07 11:09 ` Jonathan Cameron
2025-05-07 12:03 ` Shuai Xue
2025-05-07 15:36 ` Steven Rostedt
2025-05-08 1:24 ` Shuai Xue [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f88d35e2-c739-4432-a7fa-35c8a2dd2e9a@linux.alibaba.com \
--to=xueshuai@linux.alibaba.com \
--cc=anil.s.keshavamurthy@intel.com \
--cc=bhelgaas@google.com \
--cc=bp@alien8.de \
--cc=davem@davemloft.net \
--cc=helgaas@kernel.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=mark.rutland@arm.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=naveen@kernel.org \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tianruidong@linux.alibaba.com \
--cc=tony.luck@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox