All of lore.kernel.org
 help / color / mirror / Atom feed
From: Souptick Joarder <jrdr.linux@gmail.com>
To: rppt@linux.ibm.com
Cc: Michal Hocko <mhocko@suse.com>, Heiko Stuebner <heiko@sntech.de>,
	Peter Zijlstra <peterz@infradead.org>,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	Linux-MM <linux-mm@kvack.org>,
	linux1394-devel@lists.sourceforge.net,
	Marek Szyprowski <m.szyprowski@samsung.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	oleksandr_andrushchenko@epam.com, joro@8bytes.org,
	Russell King - ARM Linux <linux@armlinux.org.uk>,
	Matthew Wilcox <willy@infradead.org>,
	airlied@linux.ie, linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org, treding@nvidia.com,
	linux-media@vger.kernel.org, Kees Cook <keescook@chromium.org>,
	pawel@osciak.com, Rik van Riel <riel@surriel.com>,
	iommu@lists.linux-foundation.org, rppt@linux.vnet.ibm.com,
	Boris Ostrovsky <boris.ostrovsky@oracle.com>,
	mchehab@kernel.org, iamjoonsoo.kim@lge.com, vbabka@suse.cz,
	Juergen Gross <jgross@suse.>
Subject: Re: [PATCH 1/9] mm: Introduce new vm_insert_range API
Date: Sat, 17 Nov 2018 12:26:38 +0530	[thread overview]
Message-ID: <CAFqt6zYp0j999WXw9Jus0oZMjADQQkPfso8btv6du6L9CE3PXA__34433.3190042109$1542437525$gmane$org@mail.gmail.com> (raw)
In-Reply-To: <20181116182836.GB17088@rapoport-lnx>

On Fri, Nov 16, 2018 at 11:59 PM Mike Rapoport <rppt@linux.ibm.com> wrote:
>
> On Thu, Nov 15, 2018 at 09:15:30PM +0530, Souptick Joarder wrote:
> > Previouly drivers have their own way of mapping range of
> > kernel pages/memory into user vma and this was done by
> > invoking vm_insert_page() within a loop.
> >
> > As this pattern is common across different drivers, it can
> > be generalized by creating a new function and use it across
> > the drivers.
> >
> > vm_insert_range is the new API which will be used to map a
> > range of kernel memory/pages to user vma.
> >
> > Signed-off-by: Souptick Joarder <jrdr.linux@gmail.com>
> > Reviewed-by: Matthew Wilcox <willy@infradead.org>
> > ---
> >  include/linux/mm_types.h |  3 +++
> >  mm/memory.c              | 28 ++++++++++++++++++++++++++++
> >  mm/nommu.c               |  7 +++++++
> >  3 files changed, 38 insertions(+)
> >
> > diff --git a/include/linux/mm_types.h b/include/linux/mm_types.h
> > index 5ed8f62..15ae24f 100644
> > --- a/include/linux/mm_types.h
> > +++ b/include/linux/mm_types.h
> > @@ -523,6 +523,9 @@ extern void tlb_gather_mmu(struct mmu_gather *tlb, struct mm_struct *mm,
> >  extern void tlb_finish_mmu(struct mmu_gather *tlb,
> >                               unsigned long start, unsigned long end);
> >
> > +int vm_insert_range(struct vm_area_struct *vma, unsigned long addr,
> > +                     struct page **pages, unsigned long page_count);
> > +
> >  static inline void init_tlb_flush_pending(struct mm_struct *mm)
> >  {
> >       atomic_set(&mm->tlb_flush_pending, 0);
> > diff --git a/mm/memory.c b/mm/memory.c
> > index 15c417e..da904ed 100644
> > --- a/mm/memory.c
> > +++ b/mm/memory.c
> > @@ -1478,6 +1478,34 @@ static int insert_page(struct vm_area_struct *vma, unsigned long addr,
> >  }
> >
> >  /**
> > + * vm_insert_range - insert range of kernel pages into user vma
> > + * @vma: user vma to map to
> > + * @addr: target user address of this page
> > + * @pages: pointer to array of source kernel pages
> > + * @page_count: no. of pages need to insert into user vma
> > + *
> > + * This allows drivers to insert range of kernel pages they've allocated
> > + * into a user vma. This is a generic function which drivers can use
> > + * rather than using their own way of mapping range of kernel pages into
> > + * user vma.
>
> Please add the return value and context descriptions.
>
> > + */
> > +int vm_insert_range(struct vm_area_struct *vma, unsigned long addr,
> > +                     struct page **pages, unsigned long page_count)
> > +{
> > +     unsigned long uaddr = addr;
> > +     int ret = 0, i;
> > +
> > +     for (i = 0; i < page_count; i++) {
> > +             ret = vm_insert_page(vma, uaddr, pages[i]);
> > +             if (ret < 0)
> > +                     return ret;
> > +             uaddr += PAGE_SIZE;
> > +     }
> > +
> > +     return ret;
> > +}
> > +
> > +/**
> >   * vm_insert_page - insert single page into user vma
> >   * @vma: user vma to map to
> >   * @addr: target user address of this page
> > diff --git a/mm/nommu.c b/mm/nommu.c
> > index 749276b..d6ef5c7 100644
> > --- a/mm/nommu.c
> > +++ b/mm/nommu.c
> > @@ -473,6 +473,13 @@ int vm_insert_page(struct vm_area_struct *vma, unsigned long addr,
> >  }
> >  EXPORT_SYMBOL(vm_insert_page);
> >
> > +int vm_insert_range(struct vm_area_struct *vma, unsigned long addr,
> > +                     struct page **pages, unsigned long page_count)
> > +{
> > +     return -EINVAL;
> > +}
> > +EXPORT_SYMBOL(vm_insert_range);
> > +
> >  /*
> >   *  sys_brk() for the most part doesn't need the global kernel
> >   *  lock, except when an application is doing something nasty
> > --
> > 1.9.1
> >
>
> --
> Sincerely yours,
> Mike.
>

Sure I will wait for some time to get additional review comments and
add all of those requested changes in v2.

Any further feedback on driver changes as part of this patch series ?

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  reply	other threads:[~2018-11-17  6:56 UTC|newest]

Thread overview: 73+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-15 15:45 [PATCH 1/9] mm: Introduce new vm_insert_range API Souptick Joarder
2018-11-15 15:45 ` Souptick Joarder
2018-11-15 15:45 ` Souptick Joarder
2018-11-15 18:13 ` Randy Dunlap
2018-11-15 18:13   ` Randy Dunlap
2018-11-15 18:13   ` Randy Dunlap
2018-11-16  5:30   ` Souptick Joarder
2018-11-16  5:30   ` Souptick Joarder
2018-11-16  5:30     ` Souptick Joarder
2018-11-16  5:30     ` Souptick Joarder
2018-11-16  6:40     ` Matthew Wilcox
2018-11-16  6:40       ` Matthew Wilcox
2018-11-16  6:40       ` Matthew Wilcox
2018-11-16  8:15       ` Souptick Joarder
2018-11-16  8:15       ` Souptick Joarder
2018-11-16  8:15         ` Souptick Joarder
2018-11-16  8:15         ` Souptick Joarder
2018-11-16 16:59         ` Randy Dunlap
2018-11-16 16:59         ` Randy Dunlap
2018-11-16 16:59           ` Randy Dunlap
2018-11-16 16:59           ` Randy Dunlap
2018-11-16  6:40     ` Matthew Wilcox
2018-11-15 18:13 ` Randy Dunlap
2018-11-16 17:48 ` Slavomir Kaslev
2018-11-16 17:55   ` Slavomir Kaslev
2018-11-16 17:48   ` Slavomir Kaslev
2018-11-16 17:48 ` Slavomir Kaslev
2018-11-16 18:28 ` Mike Rapoport
2018-11-16 18:28 ` Mike Rapoport
2018-11-16 18:28   ` Mike Rapoport
2018-11-16 18:28   ` Mike Rapoport
2018-11-17  6:56   ` Souptick Joarder [this message]
2018-11-17  6:56   ` Souptick Joarder
2018-11-17  6:56     ` Souptick Joarder
2018-11-17  6:56     ` Souptick Joarder
2018-11-17 14:37     ` Matthew Wilcox
2018-11-17 14:37     ` Matthew Wilcox
2018-11-17 14:37       ` Matthew Wilcox
2018-11-17 14:37       ` Matthew Wilcox
2018-11-19 15:13       ` Souptick Joarder
2018-11-19 15:13       ` Souptick Joarder
2018-11-19 15:13         ` Souptick Joarder
2018-11-19 15:13         ` Souptick Joarder
2018-11-19 16:26         ` Mike Rapoport
2018-11-19 16:26           ` Mike Rapoport
2018-11-19 16:26           ` Mike Rapoport
2018-11-19 17:45           ` Souptick Joarder
2018-11-19 17:45           ` Souptick Joarder
2018-11-19 17:45             ` Souptick Joarder
2018-11-19 17:45             ` Souptick Joarder
2018-11-23  7:19             ` Mike Rapoport
2018-11-23  7:19               ` Mike Rapoport
2018-11-23  7:19               ` Mike Rapoport
2018-11-23  7:19             ` Mike Rapoport
2018-11-19 16:26         ` Mike Rapoport
2018-11-21 11:19         ` William Kucharski
2018-11-21 11:19         ` William Kucharski
2018-11-21 11:19           ` William Kucharski
2018-11-21 11:19           ` William Kucharski
2018-11-21 12:35           ` Matthew Wilcox
2018-11-21 12:35             ` Matthew Wilcox
2018-11-21 12:35             ` Matthew Wilcox
2018-11-21 14:29             ` William Kucharski
2018-11-21 14:29             ` William Kucharski
2018-11-21 14:29             ` William Kucharski
2018-11-21 14:29               ` William Kucharski
2018-11-21 14:29               ` William Kucharski
2018-11-21 12:35           ` Matthew Wilcox
2018-11-28 15:21 ` Heiko Stübner
2018-11-28 15:21 ` Heiko Stübner
2018-11-28 15:21   ` Heiko Stübner
2018-11-28 15:21   ` Heiko Stübner
  -- strict thread matches above, loose matches on Subject: below --
2018-11-15 15:45 Souptick Joarder

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='CAFqt6zYp0j999WXw9Jus0oZMjADQQkPfso8btv6du6L9CE3PXA__34433.3190042109$1542437525$gmane$org@mail.gmail.com' \
    --to=jrdr.linux@gmail.com \
    --cc=airlied@linux.ie \
    --cc=boris.ostrovsky@oracle.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=heiko@sntech.de \
    --cc=iamjoonsoo.kim@lge.com \
    --cc=iommu@lists.linux-foundation.org \
    --cc=jgross@suse. \
    --cc=joro@8bytes.org \
    --cc=keescook@chromium.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    --cc=linux@armlinux.org.uk \
    --cc=m.szyprowski@samsung.com \
    --cc=mchehab@kernel.org \
    --cc=mhocko@suse.com \
    --cc=oleksandr_andrushchenko@epam.com \
    --cc=pawel@osciak.com \
    --cc=peterz@infradead.org \
    --cc=riel@surriel.com \
    --cc=rppt@linux.ibm.com \
    --cc=rppt@linux.vnet.ibm.com \
    --cc=sfr@canb.auug.org.au \
    --cc=treding@nvidia.com \
    --cc=vbabka@suse.cz \
    --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 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.