From: Davidlohr Bueso <dave@stgolabs.net>
To: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Cc: dan.j.williams@intel.com, ira.weiny@intel.com,
dave.jiang@intel.com, alison.schofield@intel.com,
bwidawsk@kernel.org, vishal.l.verma@intel.com,
a.manzanares@samsung.com, linux-cxl@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] cxl/mbox: Wire up irq support
Date: Fri, 21 Oct 2022 10:23:24 -0700 [thread overview]
Message-ID: <20221021172324.efg7vzrguvd7m44r@offworld> (raw)
In-Reply-To: <20221018103815.00003cb2@huawei.com>
On Tue, 18 Oct 2022, Jonathan Cameron wrote:
>Whilst I get the need for an example, I'd rather this didn't
>go in until we have that background handler in place.
One of the reasons why the bg stuff hasn't been re-posted is
because the only user currently is the sanitation work
(and hopefully maybe scan media soon), which in turn depends
on the cache-flushing thing to be picked up (unless someone
starts ranting again against wbinvd). And that is in Dave's
pmem security series which I'm hoping will be picked up for
v6.3 at some point.
So I guess we're a while away from the irq thing. I was mostly
suggesting sending an mbox-only just to layout the
pci_alloc_irq_vectors if we're not using the common table,
but per the above this might not be sooner than the pmu or
events stuff...
>Unused infrastructure tends to rot or not be quite what is
>needed.
No arguing there.
Thanks,
Davidlohr
next prev parent reply other threads:[~2022-10-21 17:23 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 3:00 [PATCH v3 0/2] cxl: Add general MSI-X/MSI irq support Davidlohr Bueso
2022-10-18 3:00 ` [PATCH 1/2] cxl/pci: Add generic " Davidlohr Bueso
2022-10-18 9:36 ` Jonathan Cameron
2022-10-18 10:52 ` Jonathan Cameron
2022-10-20 22:31 ` Davidlohr Bueso
2022-10-21 4:18 ` Ira Weiny
2022-10-21 8:49 ` Jonathan Cameron
2022-10-21 16:20 ` Davidlohr Bueso
2022-10-21 21:05 ` Ira Weiny
2022-10-21 4:14 ` Ira Weiny
2022-10-21 8:58 ` Jonathan Cameron
2022-10-21 15:58 ` Davidlohr Bueso
2022-10-22 22:17 ` Dan Williams
2022-10-18 11:17 ` Jonathan Cameron
2022-10-22 22:05 ` Dan Williams
2022-10-24 0:09 ` Ira Weiny
2022-10-24 2:08 ` Dan Williams
2022-10-24 12:36 ` Jonathan Cameron
2022-10-25 23:25 ` Bjorn Helgaas
2022-10-30 8:38 ` Christoph Hellwig
2022-11-02 17:15 ` Davidlohr Bueso
2022-11-02 22:54 ` Bjorn Helgaas
2022-11-02 23:42 ` Ira Weiny
2022-11-03 0:18 ` Davidlohr Bueso
2022-11-03 18:09 ` Jonathan Cameron
2022-11-10 3:30 ` Ira Weiny
2022-11-11 21:18 ` Davidlohr Bueso
2022-11-03 18:08 ` Jonathan Cameron
2022-10-18 3:00 ` [PATCH 2/2] cxl/mbox: Wire up " Davidlohr Bueso
2022-10-18 9:38 ` Jonathan Cameron
2022-10-21 17:23 ` Davidlohr Bueso [this message]
2022-10-22 22:14 ` Dan Williams
2022-10-22 22:06 ` Dan Williams
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=20221021172324.efg7vzrguvd7m44r@offworld \
--to=dave@stgolabs.net \
--cc=Jonathan.Cameron@huawei.com \
--cc=a.manzanares@samsung.com \
--cc=alison.schofield@intel.com \
--cc=bwidawsk@kernel.org \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=ira.weiny@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.