public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Yijing Wang <wangyijing@huawei.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>, <linux-pci@vger.kernel.org>,
	Arnd Bergmann <arnd@arndb.de>, <linux-kernel@vger.kernel.org>,
	Hanjun Guo <guohanjun@huawei.com>, <jiang.liu@huawei.com>
Subject: Re: [PATCH] PCI/VFIO: use pcie_flags_reg instead of access PCI-E Capabilities Register
Date: Tue, 2 Apr 2013 09:47:55 +0800	[thread overview]
Message-ID: <515A38CB.5030406@huawei.com> (raw)
In-Reply-To: <1364829361.2882.26.camel@bling.home>

>> @@ -1017,13 +1017,9 @@ static int vfio_cap_len(struct vfio_pci_device *vdev, u8 cap, u8 pos)
>>  		return byte;
>>  	case PCI_CAP_ID_EXP:
>>  		/* length based on version */
>> -		ret = pci_read_config_word(pdev, pos + PCI_EXP_FLAGS, &word);
>> -		if (ret)
>> -			return pcibios_err_to_errno(ret);
>> -
>>  		vdev->extended_caps = true;
>>  
>> -		if ((word & PCI_EXP_FLAGS_VERS) == 1)
>> +		if ((pdev->pcie_flags_reg & PCI_EXP_FLAGS_VERS) == 1)
> 
> It looks like we should be using pcie_caps_reg(pdev) here instead of
> directly accessing pcie_flags_reg.  Thanks,

That's right, I forget Myron Stowe introduced the PCIe Cap accessor function  pcie_caps_reg().
I will resend the updated patch.

Thanks!
Yijing

> 
> Alex
> 
>>  			return PCI_CAP_EXP_ENDPOINT_SIZEOF_V1;
>>  		else
>>  			return PCI_CAP_EXP_ENDPOINT_SIZEOF_V2;
> 
> 
> 
> 
> .
> 


-- 
Thanks!
Yijing


      reply	other threads:[~2013-04-02  1:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-27  9:05 [PATCH] PCI/VFIO: use pcie_flags_reg instead of access PCI-E Capabilities Register Yijing Wang
2013-04-01 15:16 ` Alex Williamson
2013-04-02  1:47   ` Yijing Wang [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=515A38CB.5030406@huawei.com \
    --to=wangyijing@huawei.com \
    --cc=alex.williamson@redhat.com \
    --cc=arnd@arndb.de \
    --cc=bhelgaas@google.com \
    --cc=guohanjun@huawei.com \
    --cc=jiang.liu@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.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