[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20221012180136.tc3ryjumquvnaqk2@offworld>
Date: Wed, 12 Oct 2022 11:01:36 -0700
From: Davidlohr Bueso <dave@...olabs.net>
To: ira.weiny@...el.com
Cc: Dan Williams <dan.j.williams@...el.com>,
Alison Schofield <alison.schofield@...el.com>,
Vishal Verma <vishal.l.verma@...el.com>,
Ben Widawsky <bwidawsk@...nel.org>,
Steven Rostedt <rostedt@...dmis.org>,
Jonathan Cameron <Jonathan.Cameron@...wei.com>,
linux-kernel@...r.kernel.org, linux-cxl@...r.kernel.org
Subject: Re: [RFC V2 PATCH 11/11] cxl/mem: Wire up event interrupts
On Mon, 10 Oct 2022, ira.weiny@...el.com wrote:
>From: Ira Weiny <ira.weiny@...el.com>
>
>CXL device events are signaled via interrupts. Each event log may have
>a different interrupt message number. These message numbers are
>reported in the Get Event Interrupt Policy mailbox command.
>
>Create an infrastructure to query the max vectors required for the CXL
>device. Add event interrupt information that infrastructure. Set up a
>handler for each event log.
>
>Davidlohr suggested the generic vector code.
So this should be a separate patch, and out of the event series altogether.
There are a number of interested parties for irq support, and imo the
generic vector stuff should be a first dependency to all of them.
I've sent out a patch with some updates you did. I also kept the whole
table populated with nil callbacks as I believe this documents the TODO
nicely.
Thanks,
Davidlohr
Powered by blists - more mailing lists