All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicholas Piggin <npiggin@gmail.com>
To: akpm@linux-foundation.org, borntraeger@de.ibm.com,
	catalin.marinas@arm.com, david@redhat.com, frankja@linux.ibm.com,
	imbrenda@linux.ibm.com, mingo@redhat.com,
	mm-commits@vger.kernel.org, rientjes@google.com,
	tglx@linutronix.de, urezki@gmail.com
Subject: Re: + kvm-s390-fix-for-hugepage-vmalloc.patch added to -mm tree
Date: Mon, 14 Jun 2021 10:58:38 +1000	[thread overview]
Message-ID: <1623631892.c5eaco2ojh.astroid@bobo.none> (raw)
In-Reply-To: <20210608210623.oyQ1Gh4H3%akpm@linux-foundation.org>

Excerpts from akpm@linux-foundation.org's message of June 9, 2021 7:06 am:
> 
> The patch titled
>      Subject: KVM: s390: fix for hugepage vmalloc
> has been added to the -mm tree.  Its filename is
>      kvm-s390-fix-for-hugepage-vmalloc.patch
> 
> This patch should soon appear at
>     https://ozlabs.org/~akpm/mmots/broken-out/kvm-s390-fix-for-hugepage-vmalloc.patch
> and later at
>     https://ozlabs.org/~akpm/mmotm/broken-out/kvm-s390-fix-for-hugepage-vmalloc.patch
> 
> Before you just go and hit "reply", please:
>    a) Consider who else should be cc'ed
>    b) Prefer to cc a suitable mailing list as well
>    c) Ideally: find the original patch on the mailing list and do a
>       reply-to-all to that, adding suitable additional cc's
> 
> *** Remember to use Documentation/process/submit-checklist.rst when testing your code ***
> 
> The -mm tree is included into linux-next and is updated
> there every 3-4 working days
> 
> ------------------------------------------------------
> From: Claudio Imbrenda <imbrenda@linux.ibm.com>
> Subject: KVM: s390: fix for hugepage vmalloc
> 
> The Create Secure Configuration Ultravisor Call does not support using
> large pages for the virtual memory area.  This is a hardware limitation.
> 
> This patch replaces the vzalloc call with a longer but equivalent
> __vmalloc_node_range call, also setting the VM_NO_HUGE_VMAP flag, to
> guarantee that this allocation will not be performed with large pages.
> 
> Link: https://lkml.kernel.org/r/20210608180618.477766-3-imbrenda@linux.ibm.com
> Signed-off-by: Claudio Imbrenda <imbrenda@linux.ibm.com>
> Reviewed-by: Janosch Frank <frankja@linux.ibm.com>
> Fixes: 121e6f3258fe393e22c3 ("mm/vmalloc: hugepage vmalloc mappings")

Hmm, s390 does not select HAVE_ARCH_HUGE_VMALLOC so it was intended that 
"mm/vmalloc: hugepage vmalloc mappings" does not introduce huge vmallocs
for you.

I can't see how this would happen, any clue what I'm missing?

Thanks,
Nick

> Acked-by: Christian Borntraeger <borntraeger@de.ibm.com>	[s390]
> Cc: Nicholas Piggin <npiggin@gmail.com>
> Cc: Uladzislau Rezki (Sony) <urezki@gmail.com>
> Cc: Catalin Marinas <catalin.marinas@arm.com>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Cc: Ingo Molnar <mingo@redhat.com>
> Cc: David Rientjes <rientjes@google.com>
> Cc: Janosch Frank <frankja@linux.ibm.com>
> Cc: David Hildenbrand <david@redhat.com>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> ---
> 
>  arch/s390/kvm/pv.c |    5 ++++-
>  1 file changed, 4 insertions(+), 1 deletion(-)
> 
> --- a/arch/s390/kvm/pv.c~kvm-s390-fix-for-hugepage-vmalloc
> +++ a/arch/s390/kvm/pv.c
> @@ -140,7 +140,10 @@ static int kvm_s390_pv_alloc_vm(struct k
>  	/* Allocate variable storage */
>  	vlen = ALIGN(virt * ((npages * PAGE_SIZE) / HPAGE_SIZE), PAGE_SIZE);
>  	vlen += uv_info.guest_virt_base_stor_len;
> -	kvm->arch.pv.stor_var = vzalloc(vlen);
> +	kvm->arch.pv.stor_var = __vmalloc_node_range(vlen, PAGE_SIZE, VMALLOC_START, VMALLOC_END,
> +						     GFP_KERNEL | __GFP_ZERO, PAGE_KERNEL,
> +						     VM_NO_HUGE_VMAP, NUMA_NO_NODE,
> +						     __builtin_return_address(0));
>  	if (!kvm->arch.pv.stor_var)
>  		goto out_err;
>  	return 0;
> _
> 
> Patches currently in -mm which might be from imbrenda@linux.ibm.com are
> 
> mm-vmalloc-export-__vmalloc_node_range.patch
> kvm-s390-fix-for-hugepage-vmalloc.patch
> 
> 

  reply	other threads:[~2021-06-14  0:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-08 21:06 + kvm-s390-fix-for-hugepage-vmalloc.patch added to -mm tree akpm
2021-06-14  0:58 ` Nicholas Piggin [this message]
2021-06-14  1:13   ` Nicholas Piggin
2021-06-14 12:37     ` Christian Borntraeger

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=1623631892.c5eaco2ojh.astroid@bobo.none \
    --to=npiggin@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=borntraeger@de.ibm.com \
    --cc=catalin.marinas@arm.com \
    --cc=david@redhat.com \
    --cc=frankja@linux.ibm.com \
    --cc=imbrenda@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=mm-commits@vger.kernel.org \
    --cc=rientjes@google.com \
    --cc=tglx@linutronix.de \
    --cc=urezki@gmail.com \
    /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.