linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Junxiao Chang <junxiao.chang@intel.com>
Cc: kirill.shutemov@linux.intel.com, mhocko@suse.com,
	jmarchan@redhat.com, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org, mike.kravetz@oracle.com,
	muchun.song@linux.dev
Subject: Re: [PATCH] mm: fix hugetlb page unmap count balance issue
Date: Fri, 12 May 2023 14:03:53 -0700	[thread overview]
Message-ID: <20230512140353.8b95e8cb024c8e7a1a3b03c1@linux-foundation.org> (raw)
In-Reply-To: <20230512072036.1027784-1-junxiao.chang@intel.com>

On Fri, 12 May 2023 15:20:36 +0800 Junxiao Chang <junxiao.chang@intel.com> wrote:

> hugetlb page usually is mapped with pmd, but occasionally it might be
> mapped with pte. QEMU can use udma-buf to create host dmabufs for guest
> framebuffers. When QEMU is launched with parameter "hugetlb=on",
> udmabuffer driver maps hugetlb page with pte in page fault handler.

Are there any other situations in which a hugetlb page is mapped in
this fashion?

If not, can QEMU be changed to map with a pmd?

So we get one less weird special case in MM.


  reply	other threads:[~2023-05-12 21:03 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-12  7:20 Junxiao Chang
2023-05-12 21:03 ` Andrew Morton [this message]
2023-05-15  0:08   ` Chang, Junxiao
2023-05-12 21:26 ` James Houghton
2023-05-12 23:29   ` Mike Kravetz
2023-05-15  0:44     ` Chang, Junxiao
2023-05-15 17:04     ` Mike Kravetz
2023-05-16 22:34       ` Mike Kravetz
2023-06-07 19:03         ` Andrew Morton
2023-06-07 20:53           ` Mike Kravetz
2023-06-07 21:00             ` Andrew Morton
2023-06-07 21:16               ` Mike Kravetz
2023-06-08  7:59               ` Greg Kroah-Hartman
2023-06-07 19:27         ` David Hildenbrand
2023-06-19 12:27       ` Gerd Hoffmann
2023-06-20  6:23         ` Kasireddy, Vivek

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=20230512140353.8b95e8cb024c8e7a1a3b03c1@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=jmarchan@redhat.com \
    --cc=junxiao.chang@intel.com \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.com \
    --cc=mike.kravetz@oracle.com \
    --cc=muchun.song@linux.dev \
    /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