All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shmulik Ladkani <shmulik.ladkani@ravellosystems.com>
To: Miao Yan <yanmiaobest@gmail.com>
Cc: dmitry@daynix.com, jasowang@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2 2/4] net/vmxnet3: return correct value for VMXNET3_CMD_GET_DID_* command
Date: Tue, 22 Dec 2015 22:49:18 +0200	[thread overview]
Message-ID: <20151222224918.704b58b2@halley> (raw)
In-Reply-To: <1450765104-26135-3-git-send-email-yanmiaobest@gmail.com>

Hi,

On Mon, 21 Dec 2015 22:18:22 -0800 Miao Yan <yanmiaobest@gmail.com> wrote:
> VMXNET3_CMD_GET_DID_LO should return PCI ID of the device
> and VMXNET3_CMD_GET_DID_HI should return vmxnet3 revision ID.
> 
> This behavior can be observed by the following steps:
> 
> 1) run a Linux distro on esxi server
> 2) modify vmxnet3 Linux driver to read DID_HI and DID_LO:
> 
>   VMXNET3_WRITE_BAR1_REG(adapter, VMXNET3_REG_CMD, VMXNET3_CMD_GET_DID_LO);
>   lo =  VMXNET3_READ_BAR1_REG(adapter, VMXNET3_REG_CMD);
> 
>   VMXNET3_WRITE_BAR1_REG(adapter, VMXNET3_REG_CMD, VMXNET3_CMD_GET_DID_HI);
>   high =  VMXNET3_READ_BAR1_REG(adapter, VMXNET3_REG_CMD);
>   pr_info("vmxnet3 DID lo: 0x%x, high: 0x%x\n", lo, high);
> 
> The kernel log will have something like the following message:
> 
>   [ 7005.111170] vmxnet3 DID lo: 0x7b0, high: 0x1

[...]

> +    case VMXNET3_CMD_GET_DID_HI:
> +        ret = VMXNET3_DEVICE_REVISION;
> +        break;
> +

Do we know whether VMXNET3_DEVICE_REVISION needs to be returned, or
should it be VMXNET3_DEVICE_VERSION instead?

I see both are currently defined as 1, but I assume this could
potentially be changed in the future.

How can we tell what's the right semantics for VMXNET3_CMD_GET_DID_HI?

Regards,
Shmulik

  reply	other threads:[~2015-12-22 20:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-22  6:18 [Qemu-devel] [PATCH v2 0/4] correct some register return values for vxmnet3 Miao Yan
2015-12-22  6:18 ` [Qemu-devel] [PATCH v2 1/4] net/vmxnet3: return 1 on device activation failure Miao Yan
2015-12-22 20:41   ` Shmulik Ladkani
2015-12-22 21:13     ` Shmulik Ladkani
2015-12-22  6:18 ` [Qemu-devel] [PATCH v2 2/4] net/vmxnet3: return correct value for VMXNET3_CMD_GET_DID_* command Miao Yan
2015-12-22 20:49   ` Shmulik Ladkani [this message]
2015-12-23  3:02     ` Miao Yan
2015-12-22 21:17   ` Shmulik Ladkani
2015-12-22  6:18 ` [Qemu-devel] [PATCH v2 3/4] net/vmxnet3: return correct value for VMXNET3_CMD_GET_DEV_EXTRA_INFO Miao Yan
2015-12-22 20:51   ` Shmulik Ladkani
2015-12-22  6:18 ` [Qemu-devel] [PATCH v2 4/4] net/vmxnet3: return 0 on unknown command Miao Yan

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=20151222224918.704b58b2@halley \
    --to=shmulik.ladkani@ravellosystems.com \
    --cc=dmitry@daynix.com \
    --cc=jasowang@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=yanmiaobest@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.