From: Adam Young <admiyo@amperemail.onmicrosoft.com>
To: Adam Young <admiyo@os.amperecomputing.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Jeremy Kerr <jk@codeconstruct.com.au>,
Matt Johnston <matt@codeconstruct.com.au>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Sudeep Holla <sudeep.holla@arm.com>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Huisong Li <lihuisong@huawei.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v45 0/7] MCTP over PCC
Date: Mon, 27 Jul 2026 12:20:33 -0400 [thread overview]
Message-ID: <1957e9cc-dbbf-4bad-b0ce-20ce69ae2c01@amperemail.onmicrosoft.com> (raw)
In-Reply-To: <20260721175258.87600-1-admiyo@os.amperecomputing.com>
On 7/21/26 13:52, Adam Young wrote:
> From: Linux Bot <linuxbot@amperecomputing.com>
>
> THis patch sereis is long lived, and the main
> changelog will saty with the MCTP over PCC patch.
> Recent changes in AI code review haved shown required
> fixes in the PC mailbox layer. The main changes to this
> patch series are the addition of those patches.
>
> Adam Young (7):
> mailbox/pcc.c: shmem map/unmap startup/teardown
> mailbox/pcc.c: ignore errors on type 4 channels.
> mailbox/pcc.c: report errors for PCC clients
> mailbox/pcc.c: add query channel function
> mctp pcc: Implement MCTP over PCC Transport
> synchronize IRQ before releasing shared memory
> wrap pchan->chan_in_use in READ/WRITE_ONCE
>
> MAINTAINERS | 5 +
> drivers/mailbox/pcc.c | 112 ++++++---
> drivers/net/mctp/Kconfig | 15 ++
> drivers/net/mctp/Makefile | 1 +
> drivers/net/mctp/mctp-pcc.c | 466 ++++++++++++++++++++++++++++++++++++
> include/acpi/pcc.h | 9 +
> 6 files changed, 576 insertions(+), 32 deletions(-)
> create mode 100644 drivers/net/mctp/mctp-pcc.c
>
I am seeking feedback from both the PCC and the Networking teams on how
to make progress here. The MCTP Driver can be made functional with no
changes to the PCC layer, but it will have potential race conditions.
Those will not be triggerable on the known hardware. Can this driver go
in as is, and we pursue the PCC fixes afterwards?
If not, the PCC fixes are blocking a driver that has been through a
couple years worth of code review, and should be prioritized. I put
them all into this one patch series to simplify my own organization, and
to provide a unified narrative for the networking reviewers. However,
the PCC code tends to be reviewed in linux-arm, and this organization is
making it harder for people on that team. I have been missing messages
between reviewers.
At this point, I know that at least one of the patches in the PCC
portion of this series needs to be rebased upon work by Sudeep Holla and
Huisong Li. I am reluctant to resubmit them right now for feat of
generating unnecessary churn. There code also obviates another patch in
this series, which shows that we are addressing similar issues.
prev parent reply other threads:[~2026-07-27 16:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-21 17:52 [PATCH v45 0/7] MCTP over PCC Adam Young
2026-07-21 17:52 ` [PATCH v45 1/7] mailbox/pcc.c: shmem map/unmap startup/teardown Adam Young
2026-07-24 17:59 ` Adam Young
2026-08-11 17:34 ` Jassi Brar
2026-08-13 5:00 ` Sudeep Holla
2026-07-21 17:52 ` [PATCH v45 2/7] mailbox/pcc.c: ignore errors on type 4 channels Adam Young
2026-07-22 8:55 ` Sudeep Holla
2026-07-22 17:04 ` Adam Young
2026-07-21 17:52 ` [PATCH v45 3/7] mailbox/pcc.c: report errors for PCC clients Adam Young
2026-07-22 9:07 ` Sudeep Holla
2026-07-22 17:07 ` Adam Young
2026-07-21 17:52 ` [PATCH v45 4/7] mailbox/pcc.c: add query channel function Adam Young
2026-07-21 17:52 ` [PATCH v45 5/7] mctp pcc: Implement MCTP over PCC Transport Adam Young
2026-07-21 17:52 ` [PATCH v45 6/7] synchronize IRQ before releasing shared memory Adam Young
2026-07-21 17:52 ` [PATCH v45 7/7] wrap pchan->chan_in_use in READ/WRITE_ONCE Adam Young
2026-07-22 8:50 ` Sudeep Holla
2026-07-22 18:58 ` Adam Young
2026-07-27 16:20 ` Adam Young [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=1957e9cc-dbbf-4bad-b0ce-20ce69ae2c01@amperemail.onmicrosoft.com \
--to=admiyo@amperemail.onmicrosoft.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=admiyo@os.amperecomputing.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jk@codeconstruct.com.au \
--cc=kuba@kernel.org \
--cc=lihuisong@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@codeconstruct.com.au \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sudeep.holla@arm.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