public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Ira Weiny <ira.weiny@intel.com>
To: Dan Williams <dan.j.williams@intel.com>, <linux-cxl@vger.kernel.org>
Cc: Ard Biesheuvel <ardb@kernel.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	Ira Weiny <ira.weiny@intel.com>,
	Jonathan Cameron <Jonathan.Cameron@huawei.com>,
	<vishal.l.verma@intel.com>, <alison.schofield@intel.com>,
	<linux-acpi@vger.kernel.org>
Subject: Re: [PATCH] acpi/ghes: Remove CXL CPER notifications
Date: Sun, 18 Feb 2024 13:54:18 -0800	[thread overview]
Message-ID: <65d27c8a8cb95_16949a2943e@iweiny-mobl.notmuch> (raw)
In-Reply-To: <170820177849.631006.8893584762602010898.stgit@dwillia2-xfh.jf.intel.com>

Dan Williams wrote:
> Initial tests with the CXL CPER implementation identified that error
> reports were being duplicated in the log and the trace event [1].  Then
> it was discovered that the notification handler took sleeping locks
> while the GHES event handling runs in spin_lock_irqsave() context [2]
> 
> Given multiple bugs to fix and how late it is in the development cycle,
> remove the CXL hookup for now and try again during the next merge
> window.
> 
> Cc: Ard Biesheuvel <ardb@kernel.org>
> Cc: Rafael J. Wysocki <rafael@kernel.org>
> Cc: Ira Weiny <ira.weiny@intel.com>
> Cc: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> Link: http://lore.kernel.org/r/20240108165855.00002f5a@Huawei.com [1]
> Closes: http://lore.kernel.org/r/b963c490-2c13-4b79-bbe7-34c6568423c7@moroto.mountain [2]
> Signed-off-by: Dan Williams <dan.j.williams@intel.com>

Dan should we add the following hunk to remove that dead code for now?

With or without this hunk.

Reviewed-by: Ira Weiny <ira.weiny@intel.com>

diff --git a/include/linux/cxl-event.h b/include/linux/cxl-event.h
index 03fa6d50d46f..f4934d0d1fb2 100644
--- a/include/linux/cxl-event.h
+++ b/include/linux/cxl-event.h
@@ -114,30 +114,4 @@ enum cxl_event_type {
        CXL_CPER_EVENT_MEM_MODULE,
 };
 
-#define CPER_CXL_DEVICE_ID_VALID               BIT(0)
-#define CPER_CXL_DEVICE_SN_VALID               BIT(1)
-#define CPER_CXL_COMP_EVENT_LOG_VALID          BIT(2)
-struct cxl_cper_event_rec {
-       struct {
-               u32 length;
-               u64 validation_bits;
-               struct cper_cxl_event_devid {
-                       u16 vendor_id;
-                       u16 device_id;
-                       u8 func_num;
-                       u8 device_num;
-                       u8 bus_num;
-                       u16 segment_num;
-                       u16 slot_num; /* bits 2:0 reserved */
-                       u8 reserved;
-               } __packed device_id;
-               struct cper_cxl_event_sn {
-                       u32 lower_dw;
-                       u32 upper_dw;
-               } __packed dev_serial_num;
-       } __packed hdr;
-
-       union cxl_event event;
-} __packed;
-
 #endif /* _LINUX_CXL_EVENT_H */

  reply	other threads:[~2024-02-18 21:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-17 20:29 [PATCH] acpi/ghes: Remove CXL CPER notifications Dan Williams
2024-02-18 21:54 ` Ira Weiny [this message]
2024-02-18 22:49   ` Dan Williams
2024-02-18 22:48 ` Dan Williams
2024-02-19 11:47 ` Jonathan Cameron

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=65d27c8a8cb95_16949a2943e@iweiny-mobl.notmuch \
    --to=ira.weiny@intel.com \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=alison.schofield@intel.com \
    --cc=ardb@kernel.org \
    --cc=dan.j.williams@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-cxl@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=vishal.l.verma@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