qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jason Wang <jasowang@redhat.com>
To: Guenter Roeck <linux@roeck-us.net>, Bin Meng <bmeng.cn@gmail.com>
Cc: "Jean-Christophe Dubois" <jcd@tribudubois.net>,
	"Peter Maydell" <peter.maydell@linaro.org>,
	qemu-arm <qemu-arm@nongnu.org>,
	"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
	"Philippe Mathieu-Daudé" <f4bug@amsat.org>
Subject: Re: [PATCH] hw/net/imx_fec: return 0xffff when accessing non-existing PHY
Date: Thu, 6 May 2021 10:24:52 +0800	[thread overview]
Message-ID: <982bc15e-1e88-8871-54b4-3dc74f540727@redhat.com> (raw)
In-Reply-To: <bffabe57-013a-1aca-e854-38a211738049@roeck-us.net>


在 2021/5/3 上午12:14, Guenter Roeck 写道:
> On 5/2/21 9:09 AM, Bin Meng wrote:
>> On Mon, May 3, 2021 at 12:03 AM Guenter Roeck <linux@roeck-us.net> wrote:
>>> If a PHY does not exist, attempts to read from it should return 0xffff.
>>> Otherwise the Linux kernel will believe that a PHY is there and select
>>> the non-existing PHY. This in turn will result in network errors later
>>> on since the real PHY is not selected or configured.
>>>
>>> Since reading from or writing to a non-existing PHY is not an emulation
>>> error, replace guest error messages with traces.
>>>
>>> Fixes: 461c51ad4275 ("Add a phy-num property to the i.MX FEC emulator")
>>> Cc: Jean-Christophe Dubois <jcd@tribudubois.net>
>>> Signed-off-by: Guenter Roeck <linux@roeck-us.net>
>>> ---
>>>   hw/net/imx_fec.c    | 8 +++-----
>>>   hw/net/trace-events | 2 ++
>>>   2 files changed, 5 insertions(+), 5 deletions(-)
>>>
>>> diff --git a/hw/net/imx_fec.c b/hw/net/imx_fec.c
>>> index f03450c028..9c7035bc94 100644
>>> --- a/hw/net/imx_fec.c
>>> +++ b/hw/net/imx_fec.c
>>> @@ -283,9 +283,8 @@ static uint32_t imx_phy_read(IMXFECState *s, int reg)
>>>       uint32_t phy = reg / 32;
>>>
>>>       if (phy != s->phy_num) {
>>> -        qemu_log_mask(LOG_GUEST_ERROR, "[%s.phy]%s: Bad phy num %u\n",
>>> -                      TYPE_IMX_FEC, __func__, phy);
>>> -        return 0;
>>> +        trace_imx_phy_read_num(phy, s->phy_num);
>>> +        return 0xffff;
>>>       }
>>>
>>>       reg %= 32;
>>> @@ -345,8 +344,7 @@ static void imx_phy_write(IMXFECState *s, int reg, uint32_t val)
>>>       uint32_t phy = reg / 32;
>>>
>>>       if (phy != s->phy_num) {
>>> -        qemu_log_mask(LOG_GUEST_ERROR, "[%s.phy]%s: Bad phy num %u\n",
>>> -                      TYPE_IMX_FEC, __func__, phy);
>>> +        trace_imx_phy_write_num(phy, s->phy_num);
>>>           return;
>>>       }
>>>
>>> diff --git a/hw/net/trace-events b/hw/net/trace-events
>>> index baf25ffa7e..ee77238d9e 100644
>>> --- a/hw/net/trace-events
>>> +++ b/hw/net/trace-events
>>> @@ -413,8 +413,10 @@ i82596_set_multicast(uint16_t count) "Added %d multicast entries"
>>>   i82596_channel_attention(void *s) "%p: Received CHANNEL ATTENTION"
>>>
>>>   # imx_fec.c
>>> +imx_phy_read_num(int phy, int configured) "read request from unconfigured phy %d (configured %d)"
>> nits: could we put this below imx_phy_read(), like you put
>> imx_phy_write_num after imx_phy_write?
>>
> Sure, makes sense. I'll wait a bit for other feedback and then resend.


Ok, please send V2.

Thanks


>
>>>   imx_phy_read(uint32_t val, int phy, int reg) "0x%04"PRIx32" <= phy[%d].reg[%d]"
>>>   imx_phy_write(uint32_t val, int phy, int reg) "0x%04"PRIx32" => phy[%d].reg[%d]"
>>> +imx_phy_write_num(int phy, int configured) "write request to unconfigured phy %d (configured %d)"
>>>   imx_phy_update_link(const char *s) "%s"
>>>   imx_phy_reset(void) ""
>>>   imx_fec_read_bd(uint64_t addr, int flags, int len, int data) "tx_bd 0x%"PRIx64" flags 0x%04x len %d data 0x%08x"
>>> --
>> Otherwise,
>> Reviewed-by: Bin Meng <bmeng.cn@gmail.com>
>> Tested-by: Bin Meng <bmeng.cn@gmail.com>
>>
> Thanks!
>
> Guenter
>



  reply	other threads:[~2021-05-06  2:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-02 16:03 [PATCH] hw/net/imx_fec: return 0xffff when accessing non-existing PHY Guenter Roeck
2021-05-02 16:09 ` Bin Meng
2021-05-02 16:14   ` Guenter Roeck
2021-05-06  2:24     ` Jason Wang [this message]
2021-05-06  3:04       ` Guenter Roeck
2021-05-02 16:12 ` Philippe Mathieu-Daudé
2021-05-06  2:23 ` Jason Wang

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=982bc15e-1e88-8871-54b4-3dc74f540727@redhat.com \
    --to=jasowang@redhat.com \
    --cc=bmeng.cn@gmail.com \
    --cc=f4bug@amsat.org \
    --cc=jcd@tribudubois.net \
    --cc=linux@roeck-us.net \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    /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).