From: Wei Yang <weiyang@linux.vnet.ibm.com>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Cc: Wei Yang <weiyang@linux.vnet.ibm.com>,
linux-pci@vger.kernel.org, netdev@vger.kernel.org,
davem@davemloft.net, Bjorn Helgaas <bhelgaas@google.com>,
Amir Vadai <amirv@mellanox.com>,
Jack Morgenstein <jackm@dev.mellanox.co.il>,
Or Gerlitz <ogerlitz@mellanox.com>
Subject: Re: [PATCH V2 net] net/mlx4_core: Preserve pci_dev_data after __mlx4_remove_one()
Date: Mon, 14 Apr 2014 09:50:30 +0800 [thread overview]
Message-ID: <20140414015029.GA5374@richard> (raw)
In-Reply-To: <534A6FA2.90800@cogentembedded.com>
On Sun, Apr 13, 2014 at 03:06:10PM +0400, Sergei Shtylyov wrote:
>Hello.
Thanks for the comments.
Changed accordingly and will send another version.
>
>On 13-04-2014 7:22, Wei Yang wrote:
>
>>pci_match_id() just match the static pci_device_id, which may return NULL if
>>someone binds the driver to a device manually using
>>/sys/bus/pci/drivers/.../new_id.
>
>>This patch wrap up a helper function __mlx4_remove_one() which does the tear
>>down function but preserve the drv_data. Functions like
>>mlx4_pci_err_detected() and mlx4_restart_one() will call this one with out
>>releasing drvdata.
>
>>Fixes: 97a5221 "net/mlx4_core: pass pci_device_id.driver_data to __mlx4_init_one during reset".
>
>>CC: Bjorn Helgaas <bhelgaas@google.com>
>>CC: Amir Vadai <amirv@mellanox.com>
>>CC: Jack Morgenstein <jackm@dev.mellanox.co.il>
>>CC: Or Gerlitz <ogerlitz@mellanox.com>
>>Signed-off-by: Wei Yang <weiyang@linux.vnet.ibm.com>
>>Acked-by: Jack Morgenstein <jackm@dev.mellanox.co.il>
>
>[...]
>
>>diff --git a/drivers/net/ethernet/mellanox/mlx4/main.c b/drivers/net/ethernet/mellanox/mlx4/main.c
>>index f0ae95f..b6d60e2 100644
>>--- a/drivers/net/ethernet/mellanox/mlx4/main.c
>>+++ b/drivers/net/ethernet/mellanox/mlx4/main.c
>[...]
>>@@ -2604,85 +2598,112 @@ err_disable_pdev:
>>
>> static int mlx4_init_one(struct pci_dev *pdev, const struct pci_device_id *id)
>> {
>>+ struct mlx4_priv *priv;
>>+ struct mlx4_dev *dev;
>>+
>> printk_once(KERN_INFO "%s", mlx4_version);
>>
>>+ priv = kzalloc(sizeof(*priv), GFP_KERNEL);
>>+ if (!priv) {
>>+ return -ENOMEM;
>>+ }
>
> {} not needed here.
>
>[...]
>>+ /* in SRIOV it is not allowed to unload the pf's
>>+ * driver while there are alive vf's */
>>+ if (mlx4_is_master(dev)) {
>>+ if (mlx4_how_many_lives_vf(dev))
>
> Could be folded into single *if*.
>
>>+ printk(KERN_ERR "Removing PF when there are assigned VF's !!!\n");
>>+ }
>>+ mlx4_stop_sense(dev);
>>+ mlx4_unregister_device(dev);
>[...]
>>+ for (p = 1; p <= dev->caps.num_ports; p++) {
>>+ mlx4_cleanup_port_info(&priv->port[p]);
>>+ mlx4_CLOSE_PORT(dev, p);
>>+ }
>>+
>>+ if (mlx4_is_master(dev))
>>+ mlx4_free_resource_tracker(dev,
>>+ RES_TR_FREE_SLAVES_ONLY);
>
> Please re-align this line so that it starts right under 'dev'.
>
>[...]
>>
>>- if (!mlx4_is_slave(dev))
>>- mlx4_free_ownership(dev);
>>+ if (mlx4_is_master(dev))
>>+ mlx4_free_resource_tracker(dev,
>>+ RES_TR_FREE_STRUCTS_ONLY);
>
> Likewise.
>
>[...]
>>@@ -2755,11 +2776,13 @@ static pci_ers_result_t mlx4_pci_err_detected(struct pci_dev *pdev,
>>
>> static pci_ers_result_t mlx4_pci_slot_reset(struct pci_dev *pdev)
>> {
>>- const struct pci_device_id *id;
>>- int ret;
>>+ struct mlx4_dev *dev = pci_get_drvdata(pdev);
>>+ struct mlx4_priv *priv = mlx4_priv(dev);
>>+ int pci_dev_data;
>
> Doesn't seem that this variable is necessary.
>
>>+ int ret;
>>
>>- id = pci_match_id(mlx4_pci_table, pdev);
>>- ret = __mlx4_init_one(pdev, id->driver_data);
>>+ pci_dev_data = priv->pci_dev_data;
>>+ ret = __mlx4_init_one(pdev, pci_dev_data);
>>
>> return ret ? PCI_ERS_RESULT_DISCONNECT : PCI_ERS_RESULT_RECOVERED;
>> }
>[...]
>
>WBR, Sergei
--
Richard Yang
Help you, Help me
prev parent reply other threads:[~2014-04-14 1:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-13 3:22 [PATCH V2 net] net/mlx4_core: Preserve pci_dev_data after __mlx4_remove_one() Wei Yang
2014-04-13 11:06 ` Sergei Shtylyov
2014-04-14 1:50 ` Wei Yang [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=20140414015029.GA5374@richard \
--to=weiyang@linux.vnet.ibm.com \
--cc=amirv@mellanox.com \
--cc=bhelgaas@google.com \
--cc=davem@davemloft.net \
--cc=jackm@dev.mellanox.co.il \
--cc=linux-pci@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ogerlitz@mellanox.com \
--cc=sergei.shtylyov@cogentembedded.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).