| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <HE1PR0401MB233169E8D223BC8809BB3DB8880F9@HE1PR0401MB2331.eurprd04.prod.outlook.com>
Date: Thu, 24 Nov 2022 17:49:32 +0000
From: Frank Li <frank.li@....com>
To: Manivannan Sadhasivam <manivannan.sadhasivam@...aro.org>
CC: "lpieralisi@...nel.org" <lpieralisi@...nel.org>,
Aisheng Dong <aisheng.dong@....com>,
"bhelgaas@...gle.com" <bhelgaas@...gle.com>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"festevam@...il.com" <festevam@...il.com>,
"imx@...ts.linux.dev" <imx@...ts.linux.dev>,
"jdmason@...zu.us" <jdmason@...zu.us>,
"kernel@...gutronix.de" <kernel@...gutronix.de>,
"kishon@...com" <kishon@...com>,
"krzysztof.kozlowski+dt@...aro.org"
<krzysztof.kozlowski+dt@...aro.org>, "kw@...ux.com" <kw@...ux.com>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
dl-linux-imx <linux-imx@....com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
"lorenzo.pieralisi@....com" <lorenzo.pieralisi@....com>,
"lznuaa@...il.com" <lznuaa@...il.com>,
"maz@...nel.org" <maz@...nel.org>,
"ntb@...ts.linux.dev" <ntb@...ts.linux.dev>,
Peng Fan <peng.fan@....com>,
"robh+dt@...nel.org" <robh+dt@...nel.org>,
"s.hauer@...gutronix.de" <s.hauer@...gutronix.de>,
"shawnguo@...nel.org" <shawnguo@...nel.org>,
"tglx@...utronix.de" <tglx@...utronix.de>
Subject: RE: [EXT] Re: [PATCH v13 1/2] PCI: endpoint: pci-epf-vntb: change
doorbell register offset calc mathod
> -----Original Message-----
> From: Manivannan Sadhasivam <manivannan.sadhasivam@...aro.org>
> Sent: Thursday, November 24, 2022 3:19 AM
> To: Frank Li <frank.li@....com>
> Cc: lpieralisi@...nel.org; Aisheng Dong <aisheng.dong@....com>;
> bhelgaas@...gle.com; devicetree@...r.kernel.org; festevam@...il.com;
> imx@...ts.linux.dev; jdmason@...zu.us; kernel@...gutronix.de;
> kishon@...com; krzysztof.kozlowski+dt@...aro.org; kw@...ux.com; linux-
> arm-kernel@...ts.infradead.org; dl-linux-imx <linux-imx@....com>; linux-
> kernel@...r.kernel.org; linux-pci@...r.kernel.org;
> lorenzo.pieralisi@....com; lznuaa@...il.com; maz@...nel.org;
> ntb@...ts.linux.dev; Peng Fan <peng.fan@....com>; robh+dt@...nel.org;
> s.hauer@...gutronix.de; shawnguo@...nel.org; tglx@...utronix.de
> Subject: [EXT] Re: [PATCH v13 1/2] PCI: endpoint: pci-epf-vntb: change
> doorbell register offset calc mathod
>
> Caution: EXT Email
>
> On Thu, Nov 24, 2022 at 12:50:35AM -0500, Frank Li wrote:
> > In drivers/ntb/hw/epf/ntb_hw_epf.c
> > ntb_epf_peer_db_set()
> > {
> > ...
> > db_offset = readl(ndev->ctrl_reg + NTB_EPF_DB_OFFSET(interrupt_num));
> > writel(db_data, ndev->db_reg + (db_entry_size * interrupt_num) +
> > db_offset);
> > ...
> > }
> >
> > The door register offset's formular is
> > offset = db_entry_size * interrupt_num + db_offset[interrupt_number]
>
> You did not mention the DB BAR here. Without that, this calculation doesn't
> make sense.
Doorbell register offset should means Base on DB BAR.
How about "The formula of door register offset refer to DB BAR"?
>
> >
> > Previous db_entry_size is 4, all db_offset is 0.
>
> s/Previous/Previously
>
> > irq | offset
> > --------------
> > 0 0
> > 1 4
> > 2 8
> > ...
> >
> > Change to db_entry_size is 0 and db_offset is 0, 4, 8, ...
> > So we can get the same map value between irq and offset. This will be
> > convenience for hardware doorbell register memory map.
> >
>
> In your irq-imx-mu-msi.c driver, the msi_address is calculated as:
>
> ```
> u64 addr = msi_data->msiir_addr + 4 * data->hwirq;
> ```
>
> So the MSI addresses itself are of 4 bytes width. So the offsets will be
> separated by 8 bytes like, 0, 8, 16,... and this won't match the MSI addresses
> as they are 4 bytes apart.
Addr is absolute physical IO address, which increased by 4. But it doesn't matter.
It should be okay if range is between 2^32.
>
> So you want to change the offset to 0, 4, 8,... by zeroing db_entry_size,
> right?
I want to directly using db_offset[irq] value as offset. It will be simple.
I am not sure why ntb_hw_epf.c use below formular.
"Db_offset[irq] + irq * db_entry_size"
Db_entry_size = 0 will be simple, all offset will be controlled by db_offset[]
You can save db_offset[] as 0, 4, 8... or 0, 8, 16 as needs.
>
> > Signed-off-by: Frank Li <Frank.Li@....com>
> > ---
> > drivers/pci/endpoint/functions/pci-epf-vntb.c | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/pci/endpoint/functions/pci-epf-vntb.c
> b/drivers/pci/endpoint/functions/pci-epf-vntb.c
> > index 04698e7995a5..0d744975f815 100644
> > --- a/drivers/pci/endpoint/functions/pci-epf-vntb.c
> > +++ b/drivers/pci/endpoint/functions/pci-epf-vntb.c
> > @@ -461,11 +461,11 @@ static int epf_ntb_config_spad_bar_alloc(struct
> epf_ntb *ntb)
> > ctrl->num_mws = ntb->num_mws;
> > ntb->spad_size = spad_size;
> >
> > - ctrl->db_entry_size = sizeof(u32);
> > + ctrl->db_entry_size = 0;
> >
> > for (i = 0; i < ntb->db_count; i++) {
> > ntb->reg->db_data[i] = 1 + i;
> > - ntb->reg->db_offset[i] = 0;
> > + ntb->reg->db_offset[i] = sizeof(u32) * i;
>
> If my above understanding is correct, then you could just reassign
> "db_entry_size" in epf_ntb_epc_msi_init().
Yes, that's one method.
I want to use one method to calc db offset for both software polling
and MSI. So overall logic should be simple.
Frank Li
>
> Thanks,
> Mani
>
> > }
> >
> > return 0;
> > --
> > 2.34.1
> >
>
> --
> மணிவண்ணன் சதாசிவம்
Powered by blists - more mailing lists