From: Suzuki K Poulose <suzuki.poulose@arm.com>
To: yuzenghui@huawei.com, linux-arm-kernel@lists.infradead.org
Cc: kvm@vger.kernel.org, marc.zyngier@arm.com,
christoffer.dall@arm.com, linux-kernel@vger.kernel.org,
eric.auger@redhat.com, zhengxiang9@huawei.com,
wanghaibin.wang@huawei.com, andrew.murray@arm.com,
kvmarm@lists.cs.columbia.edu
Subject: Re: [PATCH] kvm: arm: Skip stage2 huge mappings for unaligned ipa backed by THP
Date: Mon, 8 Apr 2019 19:40:09 +0100 [thread overview]
Message-ID: <730c25b4-dbc5-8d8b-514c-4ed8641701ce@arm.com> (raw)
In-Reply-To: <44ffad26-a407-4603-0bb6-145f7290adbe@huawei.com>
Hi Zenhui,
On 04/08/2019 04:11 PM, Zenghui Yu wrote:
> Hi Suzuki,
>
> Thanks for the reply.
>
...
>>> Hi Suzuki,
>>>
>>> Why not making use of fault_supports_stage2_huge_mapping()? Let it do
>>> some checks for us.
>>>
>>> fault_supports_stage2_huge_mapping() was intended to do a *two-step*
>>> check to tell us that can we create stage2 huge block mappings, and this
>>> check is both for hugetlbfs and THP. With commit a80868f398554842b14,
>>> we pass PAGE_SIZE as "map_size" for normal size pages (which turned out
>>> to be almost meaningless), and unfortunately the THP check no longer
>>> works.
>>
>> Thats correct.
>>
>>>
>>> So we want to rework *THP* check process. Your patch fixes the first
>>> checking-step, but the second is still missed, am I wrong?
>>
>> It fixes the step explicitly for the THP by making sure that the GPA and
>> the HVA are aligned to the map size.
>
> Yes, I understand how your patch had fixed the issue. But what I'm
> really concerned about here is the *second* checking-step in
> fault_supports_stage2_huge_mapping().
>
> We have to check if we are mapping a non-block aligned or non-block
> sized memslot, if so, we can not create block mappings for the beginning
> and end of this memslot. This is what the second part of
> fault_supports_stage2_huge_mapping() had done.
>
> I haven't seen this checking-step in your patch, did I miss something?
>
I see.
>> I don't think this calls for a VM_BUG_ON(). It is simply a case where
>> the GPA is not aligned to HVA, but for normal VMA that could be made THP.
>>
>> We had this VM_BUG_ON(), which would have never hit because we would
>> have set force_pte if they were not aligned.
>
> Yes, I agree.
>
>>>> + /* Skip memslots with unaligned IPA and user address */
>>>> + if ((gfn & mask) != (pfn & mask))
>>>> + return false;
>>>> if (pfn & mask) {
>>>> *ipap &= PMD_MASK;
>>>> kvm_release_pfn_clean(pfn);
>>>>
>>>
>>> ---8>---
>>>
>>> Rework fault_supports_stage2_huge_mapping(), let it check THP again.
>>>
>>> Signed-off-by: Zenghui Yu <yuzenghui@huawei.com>
>>> ---
>>> virt/kvm/arm/mmu.c | 11 ++++++++++-
>>> 1 file changed, 10 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/virt/kvm/arm/mmu.c b/virt/kvm/arm/mmu.c
>>> index 27c9583..5e1b258 100644
>>> --- a/virt/kvm/arm/mmu.c
>>> +++ b/virt/kvm/arm/mmu.c
>>> @@ -1632,6 +1632,15 @@ static bool
>>> fault_supports_stage2_huge_mapping(struct kvm_memory_slot *memslot,
>>> uaddr_end = uaddr_start + size;
>>>
>>> /*
>>> + * If the memslot is _not_ backed by hugetlbfs, then check if it
>>> + * can be backed by transparent hugepages.
>>> + *
>>> + * Currently only PMD_SIZE THPs are supported, revisit it later.
>>> + */
>>> + if (map_size == PAGE_SIZE)
>>> + map_size = PMD_SIZE;
>>> +
>>
>> This looks hackish. What is we support PUD_SIZE huge page in the future
>> ?
>
> Yes, this might make the code a little difficult to understand. But by
> doing so, we follow the same logic before commit a80868f398554842b14,
> that said, we do the two-step checking for normal size pages in
> fault_supports_stage2_huge_mapping(), to decide if we can create THP
> mappings for these pages.
>
> As for PUD_SIZE THPs, to be honest, I have no idea now :(
How about the following diff ?
diff --git a/virt/kvm/arm/mmu.c b/virt/kvm/arm/mmu.c
index 97b5417..98e5cec 100644
--- a/virt/kvm/arm/mmu.c
+++ b/virt/kvm/arm/mmu.c
@@ -1791,7 +1791,8 @@ static int user_mem_abort(struct kvm_vcpu *vcpu,
phys_addr_t fault_ipa,
* currently supported. This code will need to be
* updated to support other THP sizes.
*/
- if (transparent_hugepage_adjust(&pfn, &fault_ipa))
+ if (fault_supports_stage2_huge_mappings(memslot, hva, PMD_SIZE) &&
+ transparent_hugepage_adjust(&pfn, &fault_ipa))
vma_pagesize = PMD_SIZE;
}
--
2.7.4
Suzuki
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-04-08 18:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-02 11:06 [PATCH] kvm: arm: Skip stage2 huge mappings for unaligned ipa backed by THP Suzuki K Poulose
2019-04-02 15:53 ` Andrew Murray
2019-04-08 3:50 ` Zenghui Yu
2019-04-08 10:35 ` Suzuki K Poulose
2019-04-08 15:11 ` Zenghui Yu
2019-04-08 18:40 ` Suzuki K Poulose [this message]
2019-04-09 8:05 ` Zenghui Yu
2019-04-09 14:59 ` Suzuki K Poulose
2019-04-10 2:20 ` Zenghui Yu
2019-04-10 8:39 ` Suzuki K Poulose
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=730c25b4-dbc5-8d8b-514c-4ed8641701ce@arm.com \
--to=suzuki.poulose@arm.com \
--cc=andrew.murray@arm.com \
--cc=christoffer.dall@arm.com \
--cc=eric.auger@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=wanghaibin.wang@huawei.com \
--cc=yuzenghui@huawei.com \
--cc=zhengxiang9@huawei.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;
as well as URLs for NNTP newsgroup(s).