From: Alexandra Winter <wintera@linux.ibm.com>
To: Wen Gu <guwen@linux.alibaba.com>,
wenjia@linux.ibm.com, hca@linux.ibm.com, gor@linux.ibm.com,
agordeev@linux.ibm.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, kgraul@linux.ibm.com,
jaka@linux.ibm.com
Cc: borntraeger@linux.ibm.com, svens@linux.ibm.com,
alibuda@linux.alibaba.com, tonylu@linux.alibaba.com,
raspl@linux.ibm.com, schnelle@linux.ibm.com,
linux-s390@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v3 7/7] net/smc: manage system EID in SMC stack instead of ISM driver
Date: Fri, 1 Dec 2023 12:18:42 +0100 [thread overview]
Message-ID: <aab0905a-b77f-4504-a510-83c98f79b2b7@linux.ibm.com> (raw)
In-Reply-To: <1701343695-122657-8-git-send-email-guwen@linux.alibaba.com>
On 30.11.23 12:28, Wen Gu wrote:
> The System EID (SEID) is an internal EID that is used by the SMCv2
> software stack that has a predefined and constant value representing
> the s390 physical machine that the OS is executing on. So it should
> be managed by SMC stack instead of ISM driver and be consistent for
> all ISMv2 device (including virtual ISM devices) on s390 architecture.
>
> Suggested-by: Alexandra Winter <wintera@linux.ibm.com>
> Signed-off-by: Wen Gu <guwen@linux.alibaba.com>
> ---
Reviewed-by: Alexandra Winter <wintera@linux.ibm.com>
[...]
> diff --git a/net/smc/smc_ism.c b/net/smc/smc_ism.c
> index a33f861..ac88de2 100644
> --- a/net/smc/smc_ism.c
> +++ b/net/smc/smc_ism.c
[...]
> @@ -431,14 +452,8 @@ static void smcd_register_dev(struct ism_dev *ism)
>
> mutex_lock(&smcd_dev_list.mutex);
> if (list_empty(&smcd_dev_list.list)) {
> - u8 *system_eid = NULL;
> -
> - system_eid = smcd->ops->get_system_eid();
> - if (smcd->ops->supports_v2()) {
> + if (smcd->ops->supports_v2())
> smc_ism_v2_capable = true;
> - memcpy(smc_ism_v2_system_eid, system_eid,
> - SMC_MAX_EID_LEN);
> - }
> }
Just a comment:
Here we only check the first smcd device to determine whether we support v2.
Which is ok, for today's platform firmware ISM devices, as they are always the same version.
When you add virtual ISM devices (loopback-ism, virtio-ism) then this needs to be changed.
IMO the logic then needs to be "if all smcd devices support v2,
then smc_ism_v2_capable = true;
else smc_ism_v2_capable = false;"
I don't know if you would like to change that now in this patch, or later when
you add when you add the support for loopback.
next prev parent reply other threads:[~2023-12-01 11:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-30 11:28 [PATCH net-next v3 0/7] net/smc: implement SMCv2.1 virtual ISM device support Wen Gu
2023-11-30 11:28 ` [PATCH net-next v3 1/7] net/smc: Rename some variable 'fce' to 'fce_v2x' for clarity Wen Gu
2023-11-30 11:28 ` [PATCH net-next v3 2/7] net/smc: support SMCv2.x supplemental features negotiation Wen Gu
2023-11-30 11:28 ` [PATCH net-next v3 3/7] net/smc: introduce virtual ISM device support feature Wen Gu
2023-11-30 11:28 ` [PATCH net-next v3 4/7] net/smc: define a reserved CHID range for virtual ISM devices Wen Gu
2023-12-01 16:31 ` Alexandra Winter
2023-11-30 11:28 ` [PATCH net-next v3 5/7] net/smc: compatible with 128-bits extend GID of virtual ISM device Wen Gu
2023-12-01 16:30 ` Alexandra Winter
2023-12-04 9:15 ` Wenjia Zhang
2023-12-04 12:24 ` Wen Gu
2023-12-05 9:51 ` Alexandra Winter
2023-11-30 11:28 ` [PATCH net-next v3 6/7] net/smc: disable SEID on non-s390 archs where virtual ISM may be used Wen Gu
2023-11-30 11:28 ` [PATCH net-next v3 7/7] net/smc: manage system EID in SMC stack instead of ISM driver Wen Gu
2023-12-01 11:18 ` Alexandra Winter [this message]
2023-12-04 12:36 ` Wen Gu
2023-12-04 12:57 ` Alexandra Winter
2023-12-07 3:42 ` Wen Gu
2023-12-01 8:33 ` [PATCH net-next v3 0/7] net/smc: implement SMCv2.1 virtual ISM device support Wenjia Zhang
2023-12-01 16:32 ` Alexandra Winter
2023-12-04 2:01 ` Wen Gu
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=aab0905a-b77f-4504-a510-83c98f79b2b7@linux.ibm.com \
--to=wintera@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=alibuda@linux.alibaba.com \
--cc=borntraeger@linux.ibm.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gor@linux.ibm.com \
--cc=guwen@linux.alibaba.com \
--cc=hca@linux.ibm.com \
--cc=jaka@linux.ibm.com \
--cc=kgraul@linux.ibm.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=raspl@linux.ibm.com \
--cc=schnelle@linux.ibm.com \
--cc=svens@linux.ibm.com \
--cc=tonylu@linux.alibaba.com \
--cc=wenjia@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).