public inbox for linux-s390@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Claudio Imbrenda <imbrenda@linux.ibm.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
	linux-s390@vger.kernel.org, frankja@linux.ibm.com,
	cohuck@redhat.com, david@redhat.com, linux-mm@kvack.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Nicholas Piggin <npiggin@gmail.com>,
	Uladzislau Rezki <urezki@gmail.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>,
	David Rientjes <rientjes@google.com>,
	Christoph Hellwig <hch@infradead.org>
Subject: Re: [PATCH v3 2/2] KVM: s390: fix for hugepage vmalloc
Date: Thu, 10 Jun 2021 18:52:18 +0200	[thread overview]
Message-ID: <7001a6a9-d415-e826-9bf0-17032568e7b3@de.ibm.com> (raw)
In-Reply-To: <20210610184953.19bed6b4@ibm-vm>



On 10.06.21 18:49, Claudio Imbrenda wrote:
> On Thu, 10 Jun 2021 17:56:58 +0200
> Christian Borntraeger <borntraeger@de.ibm.com> wrote:
> 
>> On 10.06.21 17:42, Claudio Imbrenda wrote:
>>> 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 an almost equivalent call
>>> to the newly introduced vmalloc_no_huge function, which guarantees
>>> that only small pages will be used for the backing.
>>>
>>> The new call will not clear the allocated memory, but that has never
>>> been an actual requirement.
> 
> ^ here
> 
>>> Signed-off-by: Claudio Imbrenda <imbrenda@linux.ibm.com>
>>> Reviewed-by: Janosch Frank <frankja@linux.ibm.com>
>>> Cc: Andrew Morton <akpm@linux-foundation.org>
>>> 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: Christoph Hellwig <hch@infradead.org>
>>> ---
>>>    arch/s390/kvm/pv.c | 2 +-
>>>    1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/arch/s390/kvm/pv.c b/arch/s390/kvm/pv.c
>>> index 813b6e93dc83..ad7c6d7cc90b 100644
>>> --- a/arch/s390/kvm/pv.c
>>> +++ b/arch/s390/kvm/pv.c
>>> @@ -140,7 +140,7 @@ static int kvm_s390_pv_alloc_vm(struct kvm *kvm)
>>>    	/* 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_no_huge(vlen);
>>
>> dont we need a memset now?
> 
> no, as explained above

Makes sense.

Acked-by: Christian Borntraeger <borntraeger@de.ibm.com>

  reply	other threads:[~2021-06-10 16:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-10 15:42 [PATCH v3 0/2] mm: add vmalloc_no_huge and use it Claudio Imbrenda
2021-06-10 15:42 ` [PATCH v3 1/2] mm/vmalloc: add vmalloc_no_huge Claudio Imbrenda
2021-06-10 19:31   ` Uladzislau Rezki
2021-06-10 21:09   ` Andrew Morton
2021-06-11  8:23     ` Claudio Imbrenda
2021-06-14  2:01   ` Nicholas Piggin
2021-06-10 15:42 ` [PATCH v3 2/2] KVM: s390: fix for hugepage vmalloc Claudio Imbrenda
2021-06-10 15:56   ` Christian Borntraeger
2021-06-10 16:49     ` Claudio Imbrenda
2021-06-10 16:52       ` Christian Borntraeger [this message]
2021-06-14  1:43   ` Nicholas Piggin

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=7001a6a9-d415-e826-9bf0-17032568e7b3@de.ibm.com \
    --to=borntraeger@de.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=catalin.marinas@arm.com \
    --cc=cohuck@redhat.com \
    --cc=david@redhat.com \
    --cc=frankja@linux.ibm.com \
    --cc=hch@infradead.org \
    --cc=imbrenda@linux.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=npiggin@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox