From: Ira Weiny <ira.weiny@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: kbuild test robot <lkp@intel.com>,
Matthew Wilcox <willy@infradead.org>,
kbuild-all@01.org, linux-mm@kvack.org
Subject: Re: [PATCH v2 2/3] mm: Introduce page_shift()
Date: Thu, 25 Jul 2019 13:30:12 -0700 [thread overview]
Message-ID: <20190725203011.GA7362@iweiny-DESK2.sc.intel.com> (raw)
In-Reply-To: <20190724173055.d3c6993bfdad0f49f95b311c@linux-foundation.org>
On Wed, Jul 24, 2019 at 05:30:55PM -0700, Andrew Morton wrote:
> On Wed, 24 Jul 2019 18:40:25 +0800 kbuild test robot <lkp@intel.com> wrote:
>
> > Thank you for the patch! Yet something to improve:
> >
> > [auto build test ERROR on linus/master]
> > [cannot apply to v5.3-rc1 next-20190724]
> > [if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
> >
> > url: https://github.com/0day-ci/linux/commits/Matthew-Wilcox/Make-working-with-compound-pages-easier/20190722-030555
> > config: powerpc64-allyesconfig (attached as .config)
> > compiler: powerpc64-linux-gcc (GCC) 7.4.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.4.0 make.cross ARCH=powerpc64
> >
> > If you fix the issue, kindly add following tag
> > Reported-by: kbuild test robot <lkp@intel.com>
> >
> > Note: the linux-review/Matthew-Wilcox/Make-working-with-compound-pages-easier/20190722-030555 HEAD e1bb8b04ba8cf861b2610b0ae646ee49cb069568 builds fine.
> > It only hurts bisectibility.
> >
> > All error/warnings (new ones prefixed by >>):
> >
> > drivers/vfio/vfio_iommu_spapr_tce.c: In function 'tce_page_is_contained':
> > >> drivers/vfio/vfio_iommu_spapr_tce.c:193:9: error: called object 'page_shift' is not a function or function pointer
> > return page_shift(compound_head(page)) >= page_shift;
> > ^~~~~~~~~~
> > drivers/vfio/vfio_iommu_spapr_tce.c:179:16: note: declared here
> > unsigned int page_shift)
> > ^~~~~~~~~~
>
> This?
Looks reasonable to me. But checking around it does seem like "page_shift" is
used as a parameter or variable in quite a few other places.
Is this something to be concerned with?
Reviewed-by: Ira Weiny <ira.weiny@intel.com>
>
> --- a/drivers/vfio/vfio_iommu_spapr_tce.c~mm-introduce-page_shift-fix
> +++ a/drivers/vfio/vfio_iommu_spapr_tce.c
> @@ -176,13 +176,13 @@ put_exit:
> }
>
> static bool tce_page_is_contained(struct mm_struct *mm, unsigned long hpa,
> - unsigned int page_shift)
> + unsigned int it_page_shift)
> {
> struct page *page;
> unsigned long size = 0;
>
> - if (mm_iommu_is_devmem(mm, hpa, page_shift, &size))
> - return size == (1UL << page_shift);
> + if (mm_iommu_is_devmem(mm, hpa, it_page_shift, &size))
> + return size == (1UL << it_page_shift);
>
> page = pfn_to_page(hpa >> PAGE_SHIFT);
> /*
> @@ -190,7 +190,7 @@ static bool tce_page_is_contained(struct
> * a page we just found. Otherwise the hardware can get access to
> * a bigger memory chunk that it should.
> */
> - return page_shift(compound_head(page)) >= page_shift;
> + return page_shift(compound_head(page)) >= it_page_shift;
> }
>
> static inline bool tce_groups_attached(struct tce_container *container)
> _
>
next prev parent reply other threads:[~2019-07-25 20:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-21 10:46 [PATCH v2 0/3] Make working with compound pages easier Matthew Wilcox
2019-07-21 10:46 ` [PATCH v2 1/3] mm: Introduce page_size() Matthew Wilcox
2019-07-23 0:43 ` Ira Weiny
2019-07-23 16:02 ` Matthew Wilcox
2019-07-23 17:58 ` Ira Weiny
2019-07-23 18:14 ` Matthew Wilcox
2019-07-23 20:44 ` Ira Weiny
2019-07-23 21:03 ` Matthew Wilcox
2019-09-20 23:28 ` Andrew Morton
2019-09-21 1:09 ` Matthew Wilcox
2019-09-22 2:13 ` Weiny, Ira
2019-07-21 10:46 ` [PATCH v2 2/3] mm: Introduce page_shift() Matthew Wilcox
2019-07-23 0:44 ` Ira Weiny
2019-07-24 10:40 ` kbuild test robot
2019-07-25 0:30 ` Andrew Morton
2019-07-25 20:30 ` Ira Weiny [this message]
2019-09-23 20:30 ` Matthew Wilcox
2019-07-21 10:46 ` [PATCH v2 3/3] mm: Introduce compound_nr() Matthew Wilcox
2019-07-23 0:46 ` Ira Weiny
2019-07-23 12:55 ` [PATCH v2 0/3] Make working with compound pages easier Kirill A. Shutemov
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=20190725203011.GA7362@iweiny-DESK2.sc.intel.com \
--to=ira.weiny@intel.com \
--cc=akpm@linux-foundation.org \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=willy@infradead.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).