From: Jijie Shao <shaojijie@huawei.com>
To: <mkubecek@suse.cz>
Cc: <shaojijie@huawei.com>, <shenjian15@huawei.com>,
<wangjie125@huawei.com>, <liuyonglong@huawei.com>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH ethtool] hns3: add support dump registers for hns3 driver
Date: Wed, 23 Aug 2023 11:15:40 +0800 [thread overview]
Message-ID: <1b87e5c8-ceed-9b7a-4137-89d085e6c959@huawei.com> (raw)
In-Reply-To: <20230818085611.2483909-1-shaojijie@huawei.com>
on 2023/8/18 16:56, Jijie Shao wrote:
> Add support pretty printer for the registers of hns3 driver.
> This printer supports PF and VF, and is compatible with hns3
> drivers of earlier versions.
>
> Sample output:
>
> $ ethtool -d eth1
> [cmdq_regs]
> comm_nic_csq_baseaddr_l : 0x48168000
> comm_nic_csq_baseaddr_h : 0x00000000
> comm_nic_csq_depth : 0x00000080
> comm_nic_csq_tail : 0x00000050
> comm_nic_csq_head : 0x00000050
> comm_nic_crq_baseaddr_l : 0x48170000
> comm_nic_crq_baseaddr_h : 0x00000000
> comm_nic_crq_depth : 0x00000080
> comm_nic_crq_tail : 0x00000000
> comm_nic_crq_head : 0x00000000
> comm_vector0_cmdq_src : 0x00000000
> comm_cmdq_intr_sts : 0x00000000
> comm_cmdq_intr_en : 0x00000002
> comm_cmdq_intr_gen : 0x00000000
> [common_regs]
> misc_vector_base : 0x00000001
> pf_other_int : 0x00000040
> misc_reset_sts : 0x00000000
> misc_vector_int_sts : 0x00000000
> global_reset : 0x00000000
> fun_rst_ing : 0x00000000
> gro_en : 0x00000001
> ...
Hi，
We noticed that this patch had been stuck for several days.
Is there any problem with this patch?
Jijie Shao
next prev parent reply other threads:[~2023-08-23 3:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-18 8:56 [PATCH ethtool] hns3: add support dump registers for hns3 driver Jijie Shao
2023-08-23 3:15 ` Jijie Shao [this message]
2023-08-27 23:20 ` Michal Kubecek
2023-08-29 6:46 ` Jijie Shao
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=1b87e5c8-ceed-9b7a-4137-89d085e6c959@huawei.com \
--to=shaojijie@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=liuyonglong@huawei.com \
--cc=mkubecek@suse.cz \
--cc=netdev@vger.kernel.org \
--cc=shenjian15@huawei.com \
--cc=wangjie125@huawei.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).