All of lore.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [RFC PATCH 3/7] vfio/pci: Introduce VF token
Date: Wed, 05 Feb 2020 12:19:34 +0800	[thread overview]
Message-ID: <202002051248.1MbLORFN%lkp@intel.com> (raw)
In-Reply-To: <158085756068.9445.6284766069491778316.stgit@gimli.home>

[-- Attachment #1: Type: text/plain, Size: 3544 bytes --]

Hi Alex,

[FYI, it's a private test report for your RFC patch.]
[auto build test ERROR on vfio/next]
[also build test ERROR on pci/next linux/master linus/master v5.5 next-20200204]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]

url:    https://github.com/0day-ci/linux/commits/Alex-Williamson/vfio-pci-SR-IOV-support/20200205-071242
base:   https://github.com/awilliam/linux-vfio.git next
config: s390-defconfig (attached as .config)
compiler: s390-linux-gcc (GCC) 7.5.0
reproduce:
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # save the attached .config to linux build tree
        GCC_VERSION=7.5.0 make.cross ARCH=s390 

If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

   drivers/vfio/pci/vfio_pci.c: In function 'vfio_pci_vf_token_user_add':
>> drivers/vfio/pci/vfio_pci.c:476:49: error: 'struct pci_dev' has no member named 'physfn'; did you mean 'is_physfn'?
     pf_dev = vfio_device_get_from_dev(&vdev->pdev->physfn->dev);
                                                    ^~~~~~
                                                    is_physfn
   drivers/vfio/pci/vfio_pci.c:480:33: error: 'struct pci_dev' has no member named 'physfn'; did you mean 'is_physfn'?
     if (pci_dev_driver(vdev->pdev->physfn) != &vfio_pci_driver) {
                                    ^~~~~~
                                    is_physfn
   drivers/vfio/pci/vfio_pci.c: In function 'vfio_pci_match':
   drivers/vfio/pci/vfio_pci.c:1354:42: error: 'struct pci_dev' has no member named 'physfn'; did you mean 'is_physfn'?
       vfio_device_get_from_dev(&vdev->pdev->physfn->dev);
                                             ^~~~~~
                                             is_physfn
   drivers/vfio/pci/vfio_pci.c:1357:35: error: 'struct pci_dev' has no member named 'physfn'; did you mean 'is_physfn'?
       if (pci_dev_driver(vdev->pdev->physfn) ==
                                      ^~~~~~
                                      is_physfn
   drivers/vfio/pci/vfio_pci.c: In function 'vfio_pci_probe':
>> drivers/vfio/pci/vfio_pci.c:1458:10: error: 'struct pci_dev' has no member named 'sriov'
     if (pdev->sriov) {
             ^~

vim +476 drivers/vfio/pci/vfio_pci.c

   467	
   468	static void vfio_pci_vf_token_user_add(struct vfio_pci_device *vdev, int val)
   469	{
   470		struct vfio_device *pf_dev;
   471		struct vfio_pci_device *pf_vdev;
   472	
   473		if (!vdev->pdev->is_virtfn)
   474			return;
   475	
 > 476		pf_dev = vfio_device_get_from_dev(&vdev->pdev->physfn->dev);
   477		if (!pf_dev)
   478			return;
   479	
   480		if (pci_dev_driver(vdev->pdev->physfn) != &vfio_pci_driver) {
   481			vfio_device_put(pf_dev);
   482			return;
   483		}
   484	
   485		pf_vdev = vfio_device_data(pf_dev);
   486	
   487		mutex_lock(&pf_vdev->vf_token->lock);
   488		pf_vdev->vf_token->users += val;
   489		mutex_unlock(&pf_vdev->vf_token->lock);
   490	
   491		vfio_device_put(pf_dev);
   492	}
   493	

---
0-DAY kernel test infrastructure                 Open Source Technology Center
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org Intel Corporation

[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 18760 bytes --]

  reply	other threads:[~2020-02-05  4:19 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-04 23:05 [RFC PATCH 0/7] vfio/pci: SR-IOV support Alex Williamson
2020-02-04 23:05 ` [dpdk-dev] " Alex Williamson
2020-02-04 23:05 ` [RFC PATCH 1/7] vfio: Include optional device match in vfio_device_ops callbacks Alex Williamson
2020-02-04 23:05   ` [dpdk-dev] " Alex Williamson
2020-02-06 11:14   ` Cornelia Huck
2020-02-06 11:14     ` [dpdk-dev] " Cornelia Huck
2020-02-06 18:18     ` Alex Williamson
2020-02-06 18:18       ` [dpdk-dev] " Alex Williamson
2020-02-07  9:33       ` Cornelia Huck
2020-02-07  9:33         ` [dpdk-dev] " Cornelia Huck
2020-02-04 23:05 ` [RFC PATCH 2/7] vfio/pci: Implement match ops Alex Williamson
2020-02-04 23:05   ` [dpdk-dev] " Alex Williamson
2020-02-04 23:06 ` [RFC PATCH 3/7] vfio/pci: Introduce VF token Alex Williamson
2020-02-04 23:06   ` [dpdk-dev] " Alex Williamson
2020-02-05  4:19   ` kbuild test robot [this message]
2020-02-05  7:57   ` Liu, Yi L
2020-02-05  7:57     ` [dpdk-dev] " Liu, Yi L
2020-02-05 14:13     ` Alex Williamson
2020-02-05 14:13       ` [dpdk-dev] " Alex Williamson
2020-02-04 23:06 ` [RFC PATCH 4/7] vfio: Introduce VFIO_DEVICE_FEATURE ioctl and first user Alex Williamson
2020-02-04 23:06   ` [dpdk-dev] " Alex Williamson
2020-02-04 23:06 ` [RFC PATCH 5/7] vfio/pci: Add sriov_configure support Alex Williamson
2020-02-04 23:06   ` [dpdk-dev] " Alex Williamson
2020-02-04 23:06 ` [RFC PATCH 6/7] vfio/pci: Remove dev_fmt definition Alex Williamson
2020-02-04 23:06   ` [dpdk-dev] " Alex Williamson
2020-02-06 13:45   ` Cornelia Huck
2020-02-06 13:45     ` [dpdk-dev] " Cornelia Huck
2020-02-04 23:06 ` [RFC PATCH 7/7] vfio/pci: Cleanup .probe() exit paths Alex Williamson
2020-02-04 23:06   ` [dpdk-dev] " Alex Williamson
2020-02-04 23:17 ` [RFC PATCH 0/7] vfio/pci: SR-IOV support Alex Williamson
2020-02-04 23:17   ` [dpdk-dev] " Alex Williamson
2020-02-05  7:57   ` Liu, Yi L
2020-02-05  7:57     ` [dpdk-dev] " Liu, Yi L
2020-02-05 14:18     ` Alex Williamson
2020-02-05 14:18       ` [dpdk-dev] " Alex Williamson
2020-02-05  7:01 ` Christoph Hellwig
2020-02-05  7:01   ` [dpdk-dev] " Christoph Hellwig
2020-02-05 13:58   ` Alex Williamson
2020-02-05 13:58     ` [dpdk-dev] " Alex Williamson
2020-02-05  7:57 ` Liu, Yi L
2020-02-05  7:57   ` [dpdk-dev] " Liu, Yi L
2020-02-05 14:10   ` Alex Williamson
2020-02-05 14:10     ` [dpdk-dev] " Alex Williamson
2020-02-11 11:18 ` Jerin Jacob
2020-02-11 11:18   ` [dpdk-dev] " Jerin Jacob
2020-02-11 13:57   ` Thomas Monjalon
2020-02-11 17:06   ` Alex Williamson
2020-02-11 17:06     ` [dpdk-dev] " Alex Williamson
2020-02-11 18:03     ` Jerin Jacob
2020-02-11 18:03       ` [dpdk-dev] " Jerin Jacob

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=202002051248.1MbLORFN%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.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 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.