linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Peter Xu <peterx@redhat.com>
To: Mike Kravetz <mike.kravetz@oracle.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	Axel Rasmussen <axelrasmussen@google.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Mike Rapoport <rppt@linux.vnet.ibm.com>,
	"Kirill A . Shutemov" <kirill@shutemov.name>,
	Matthew Wilcox <willy@infradead.org>,
	Andrea Arcangeli <aarcange@redhat.com>
Subject: Re: [PATCH v3 1/4] hugetlb: Pass vma into huge_pte_alloc() and huge_pmd_share()
Date: Thu, 18 Feb 2021 18:02:24 -0500	[thread overview]
Message-ID: <20210218230224.GC6669@xz-x1> (raw)
In-Reply-To: <9d93ec4c-4cb9-c3c8-5b73-ae00c4fa9435@oracle.com>

On Thu, Feb 18, 2021 at 02:38:18PM -0800, Mike Kravetz wrote:
> I thought the error was caused by not deleting the line
> 
> 	pte_t *huge_pte_alloc(struct mm_struct *mm,
> 
> when adding
> 
> 	pte_t *huge_pte_alloc(struct mm_struct *mm, struct vm_area_struct *vma,
> 
> as above.

Sorry about that!  I'll repost.

-- 
Peter Xu



  reply	other threads:[~2021-02-18 23:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-18 21:54 [PATCH v3 0/4] hugetlb: Disable huge pmd unshare for uffd-wp Peter Xu
2021-02-18 21:54 ` [PATCH v3 1/4] hugetlb: Pass vma into huge_pte_alloc() and huge_pmd_share() Peter Xu
2021-02-18 22:13   ` Mike Kravetz
2021-02-18 22:27     ` Peter Xu
2021-02-18 22:38       ` Mike Kravetz
2021-02-18 23:02         ` Peter Xu [this message]
2021-02-18 21:55 ` [PATCH v3 2/4] hugetlb/userfaultfd: Forbid huge pmd sharing when uffd enabled Peter Xu
2021-02-18 21:55 ` [PATCH v3 3/4] mm/hugetlb: Move flush_hugetlb_tlb_range() into hugetlb.h Peter Xu
2021-02-18 21:55 ` [PATCH v3 4/4] hugetlb/userfaultfd: Unshare all pmds for hugetlbfs when register wp Peter Xu
2021-02-18 22:18   ` Mike Kravetz

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=20210218230224.GC6669@xz-x1 \
    --to=peterx@redhat.com \
    --cc=aarcange@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=axelrasmussen@google.com \
    --cc=kirill@shutemov.name \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mike.kravetz@oracle.com \
    --cc=rppt@linux.vnet.ibm.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).