From: Shiju Jose <shiju.jose@huawei.com>
To: Jonathan Cameron <jonathan.cameron@huawei.com>,
Ira Weiny <ira.weiny@intel.com>
Cc: Dan Williams <dan.j.williams@intel.com>,
Smita Koralahalli <Smita.KoralahalliChannabasappa@amd.com>,
Yazen Ghannam <yazen.ghannam@amd.com>,
Davidlohr Bueso <dave@stgolabs.net>,
Dave Jiang <dave.jiang@intel.com>,
Alison Schofield <alison.schofield@intel.com>,
"Vishal Verma" <vishal.l.verma@intel.com>,
Ard Biesheuvel <ardb@kernel.org>,
"linux-efi@vger.kernel.org" <linux-efi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-cxl@vger.kernel.org" <linux-cxl@vger.kernel.org>
Subject: RE: [PATCH RFC v3 1/6] cxl/trace: Remove uuid from event trace known events
Date: Fri, 3 Nov 2023 16:12:02 +0000 [thread overview]
Message-ID: <547d055eb85d4cee9c636c69e89a82ed@huawei.com> (raw)
In-Reply-To: <20231103142756.00000e20@Huawei.com>
>-----Original Message-----
>From: Jonathan Cameron <jonathan.cameron@huawei.com>
>Sent: 03 November 2023 14:28
>To: Ira Weiny <ira.weiny@intel.com>
>Cc: Dan Williams <dan.j.williams@intel.com>; Smita Koralahalli
><Smita.KoralahalliChannabasappa@amd.com>; Yazen Ghannam
><yazen.ghannam@amd.com>; Davidlohr Bueso <dave@stgolabs.net>; Dave
>Jiang <dave.jiang@intel.com>; Alison Schofield <alison.schofield@intel.com>;
>Vishal Verma <vishal.l.verma@intel.com>; Ard Biesheuvel <ardb@kernel.org>;
>linux-efi@vger.kernel.org; linux-kernel@vger.kernel.org; linux-
>cxl@vger.kernel.org; Shiju Jose <shiju.jose@huawei.com>
>Subject: Re: [PATCH RFC v3 1/6] cxl/trace: Remove uuid from event trace known
>events
>
>On Wed, 01 Nov 2023 14:11:18 -0700
>Ira Weiny <ira.weiny@intel.com> wrote:
>
>> The uuid printed in the well known events is redundant. The uuid
>> defines what the event was.
>>
>> Remove the uuid from the known events and only report it in the
>> generic event as it remains informative there.
>>
>> Reviewed-by: Davidlohr Bueso <dave@stgolabs.net>
>> Reviewed-by: Dan Williams <dan.j.williams@intel.com>
>> Signed-off-by: Ira Weiny <ira.weiny@intel.com>
>
>Removing the print is fine, but look like this also removes the actual trace point
>field. That's userspace ABI. Expanding it is fine, but taking fields away is more
>problematic.
>
>Are we sure we don't break anyone? Shiju, will rasdaemon be fine with this
>change?
The field hdr_uuid is removed from the common CXL_EVT_TP_entry shared by the
trace events cxl_generic_event, cxl_general_media, cxl_dram and cxl_memory_module .
rasdaemon will break because of this while processing these trace events
and also affects the corresponding error records in the SQLite data base.
Rasdaemon needs update to avoid this.
>
>Thanks,
>
>Jonathan
>
Thanks,
Shiju
>
>
>> ---
>> drivers/cxl/core/trace.h | 10 +++++-----
>> 1 file changed, 5 insertions(+), 5 deletions(-)
>>
>> diff --git a/drivers/cxl/core/trace.h b/drivers/cxl/core/trace.h index
>> a0b5819bc70b..79ed03637604 100644
>> --- a/drivers/cxl/core/trace.h
>> +++ b/drivers/cxl/core/trace.h
>> @@ -189,7 +189,6 @@ TRACE_EVENT(cxl_overflow,
>> __string(memdev, dev_name(&cxlmd->dev)) \
>> __string(host, dev_name(cxlmd->dev.parent)) \
>> __field(int, log) \
>> - __field_struct(uuid_t, hdr_uuid) \
>> __field(u64, serial) \
>> __field(u32, hdr_flags) \
>> __field(u16, hdr_handle) \
>> @@ -203,7 +202,6 @@ TRACE_EVENT(cxl_overflow,
>> __assign_str(host, dev_name((cxlmd)->dev.parent));
> \
>> __entry->log = (l);
> \
>> __entry->serial = (cxlmd)->cxlds->serial; \
>> - memcpy(&__entry->hdr_uuid, &(hdr).id, sizeof(uuid_t));
> \
>> __entry->hdr_length = (hdr).length;
> \
>> __entry->hdr_flags = get_unaligned_le24((hdr).flags);
> \
>> __entry->hdr_handle = le16_to_cpu((hdr).handle);
> \
>> @@ -212,12 +210,12 @@ TRACE_EVENT(cxl_overflow,
>> __entry->hdr_maint_op_class = (hdr).maint_op_class
>>
>> #define CXL_EVT_TP_printk(fmt, ...) \
>> - TP_printk("memdev=%s host=%s serial=%lld log=%s : time=%llu
>uuid=%pUb " \
>> + TP_printk("memdev=%s host=%s serial=%lld log=%s : time=%llu "
> \
>> "len=%d flags='%s' handle=%x related_handle=%x "
> \
>> "maint_op_class=%u : " fmt,
> \
>> __get_str(memdev), __get_str(host), __entry->serial,
> \
>> cxl_event_log_type_str(__entry->log),
> \
>> - __entry->hdr_timestamp, &__entry->hdr_uuid, __entry-
>>hdr_length,\
>> + __entry->hdr_timestamp, __entry->hdr_length,
> \
>> show_hdr_flags(__entry->hdr_flags), __entry->hdr_handle,
> \
>> __entry->hdr_related_handle, __entry->hdr_maint_op_class,
> \
>> ##__VA_ARGS__)
>> @@ -231,15 +229,17 @@ TRACE_EVENT(cxl_generic_event,
>>
>> TP_STRUCT__entry(
>> CXL_EVT_TP_entry
>> + __field_struct(uuid_t, hdr_uuid)
>> __array(u8, data, CXL_EVENT_RECORD_DATA_LENGTH)
>> ),
>>
>> TP_fast_assign(
>> CXL_EVT_TP_fast_assign(cxlmd, log, rec->hdr);
>> + memcpy(&__entry->hdr_uuid, &rec->hdr.id, sizeof(uuid_t));
>> memcpy(__entry->data, &rec->data,
>CXL_EVENT_RECORD_DATA_LENGTH);
>> ),
>>
>> - CXL_EVT_TP_printk("%s",
>> + CXL_EVT_TP_printk("uuid=%pUb %s", &__entry->hdr_uuid,
>> __print_hex(__entry->data,
>CXL_EVENT_RECORD_DATA_LENGTH)) );
>>
>>
next prev parent reply other threads:[~2023-11-03 16:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-01 21:11 [PATCH RFC v3 0/6] efi/cxl-cper: Report CPER CXL component events through trace events Ira Weiny
2023-11-01 21:11 ` [PATCH RFC v3 1/6] cxl/trace: Remove uuid from event trace known events Ira Weiny
2023-11-03 14:27 ` Jonathan Cameron
2023-11-03 16:12 ` Shiju Jose [this message]
2023-11-06 22:05 ` Ira Weiny
2023-11-07 9:38 ` Shiju Jose
2023-11-01 21:11 ` [PATCH RFC v3 2/6] cxl/events: Promote CXL event structures to a core header Ira Weiny
2023-11-01 21:11 ` [PATCH RFC v3 3/6] cxl/events: Remove UUID from non-generic event structures Ira Weiny
2023-11-01 21:11 ` [PATCH RFC v3 4/6] cxl/events: Create a CXL event union Ira Weiny
2023-11-01 21:11 ` [PATCH RFC v3 5/6] firmware/efi: Process CXL Component Events Ira Weiny
2023-11-03 0:30 ` Smita Koralahalli
2023-11-06 22:12 ` Ira Weiny
2023-11-01 21:11 ` [PATCH RFC v3 6/6] cxl/memdev: Register for and process CPER events Ira Weiny
2023-11-03 0:32 ` Smita Koralahalli
2023-11-06 22:10 ` Ira Weiny
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=547d055eb85d4cee9c636c69e89a82ed@huawei.com \
--to=shiju.jose@huawei.com \
--cc=Smita.KoralahalliChannabasappa@amd.com \
--cc=alison.schofield@intel.com \
--cc=ardb@kernel.org \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=ira.weiny@intel.com \
--cc=jonathan.cameron@huawei.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vishal.l.verma@intel.com \
--cc=yazen.ghannam@amd.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