From: Suzuki K Poulose <suzuki.poulose@arm.com>
To: yuzenghui@huawei.com, christoffer.dall@arm.com, marc.zyngier@arm.com
Cc: james.morse@arm.com, julien.thierry@arm.com,
wanghaibin.wang@huawei.com, kvmarm@lists.cs.columbia.edu,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] KVM: arm/arm64: Comments cleanup in mmu.c
Date: Mon, 25 Mar 2019 09:58:09 +0000 [thread overview]
Message-ID: <194b5370-0ed2-5dbd-9a5d-e20e4f8413ec@arm.com> (raw)
In-Reply-To: <1553500925-26000-1-git-send-email-yuzenghui@huawei.com>
On 25/03/2019 08:02, Zenghui Yu wrote:
> Some comments in virt/kvm/arm/mmu.c are outdated and incorrect.
> Get rid of these comments, to keep the code&comment correct and
> current as a whole.
>
> Only a cleanup here, no functional change.
>
> Signed-off-by: Zenghui Yu <yuzenghui@huawei.com>
> ---
> virt/kvm/arm/mmu.c | 23 +++++++++--------------
> 1 file changed, 9 insertions(+), 14 deletions(-)
>
> diff --git a/virt/kvm/arm/mmu.c b/virt/kvm/arm/mmu.c
> index ffd7acd..0a6efe7 100644
> --- a/virt/kvm/arm/mmu.c
> +++ b/virt/kvm/arm/mmu.c
> @@ -102,8 +102,7 @@ static bool kvm_is_device_pfn(unsigned long pfn)
> * @addr: IPA
> * @pmd: pmd pointer for IPA
> *
> - * Function clears a PMD entry, flushes addr 1st and 2nd stage TLBs. Marks all
> - * pages in the range dirty.
> + * Function clears a PMD entry, flushes addr 1st and 2nd stage TLBs.
> */
> static void stage2_dissolve_pmd(struct kvm *kvm, phys_addr_t addr, pmd_t *pmd)
> {
> @@ -121,8 +120,7 @@ static void stage2_dissolve_pmd(struct kvm *kvm, phys_addr_t addr, pmd_t *pmd)
> * @addr: IPA
> * @pud: pud pointer for IPA
> *
> - * Function clears a PUD entry, flushes addr 1st and 2nd stage TLBs. Marks all
> - * pages in the range dirty.
> + * Function clears a PUD entry, flushes addr 1st and 2nd stage TLBs.
> */
> static void stage2_dissolve_pud(struct kvm *kvm, phys_addr_t addr, pud_t *pudp)
> {
> @@ -899,9 +897,8 @@ int create_hyp_exec_mappings(phys_addr_t phys_addr, size_t size,
> * kvm_alloc_stage2_pgd - allocate level-1 table for stage-2 translation.
> * @kvm: The KVM struct pointer for the VM.
> *
> - * Allocates only the stage-2 HW PGD level table(s) (can support either full
> - * 40-bit input addresses or limited to 32-bit input addresses). Clears the
> - * allocated pages.
> + * Allocates only the stage-2 HW PGD level table(s) of size defined by
> + * stage2_pgd_size(kvm).
> *
> * Note we don't need locking here as this is only called when the VM is
> * created, which can only be done once.
> @@ -1451,13 +1448,11 @@ static void stage2_wp_pmds(struct kvm *kvm, pud_t *pud,
> }
>
> /**
> - * stage2_wp_puds - write protect PGD range
> - * @pgd: pointer to pgd entry
> - * @addr: range start address
> - * @end: range end address
> - *
> - * Process PUD entries, for a huge PUD we cause a panic.
> - */
> + * stage2_wp_puds - write protect PGD range
> + * @pgd: pointer to pgd entry
> + * @addr: range start address
> + * @end: range end address
> + */
Reviewed-by: Suzuki K Poulose <suzuki.poulose@arm.com>
prev parent reply other threads:[~2019-03-25 9:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-25 8:02 Zenghui Yu
2019-03-25 9:58 ` Suzuki K Poulose [this message]
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=194b5370-0ed2-5dbd-9a5d-e20e4f8413ec@arm.com \
--to=suzuki.poulose@arm.com \
--cc=christoffer.dall@arm.com \
--cc=james.morse@arm.com \
--cc=julien.thierry@arm.com \
--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 \
/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
all inboxes | Powered by JetHome®