From: gleb@redhat.com (Gleb Natapov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/3] KVM: ARM: Get rid of KVM_HPAGE_ defines
Date: Sun, 25 Aug 2013 17:05:29 +0300 [thread overview]
Message-ID: <20130825140529.GT8218@redhat.com> (raw)
In-Reply-To: <1376058613-26400-1-git-send-email-christoffer.dall@linaro.org>
On Fri, Aug 09, 2013 at 07:30:13AM -0700, Christoffer Dall wrote:
> The KVM_HPAGE_DEFINES are a little artificial on ARM, since the huge
> page size is statically defined at compile time and there is only a
> single huge page size.
>
> Now when the main kvm code relying on these defines has been moved to
> the x86 specific part of the world, we can get rid of these.
>
> Signed-off-by: Christoffer Dall <christoffer.dall@linaro.org>
> ---
>
> [Resending this because the KVM list filter caught the subject of the
> previous message due to the letter X]
>
> arch/arm/include/asm/kvm_host.h | 5 -----
> 1 file changed, 5 deletions(-)
>
> diff --git a/arch/arm/include/asm/kvm_host.h b/arch/arm/include/asm/kvm_host.h
> index 7d22517..e45a74b 100644
> --- a/arch/arm/include/asm/kvm_host.h
> +++ b/arch/arm/include/asm/kvm_host.h
> @@ -38,11 +38,6 @@
>
> #define KVM_VCPU_MAX_FEATURES 1
>
> -/* We don't currently support large pages. */
> -#define KVM_HPAGE_GFN_SHIFT(x) 0
> -#define KVM_NR_PAGE_SIZES 1
With huge page support you do have two different page sizes, but the only
code that uses those defines currently is in the x86 shadow mmu code,
so I am fine with moving gfn_to_index() into x86 specific code and getting rid
of those defines (you will probably need them when you will implement
nested HYP mode :)). But can you do it as a separate patch series and
remove the defines for all arches?
> -#define KVM_PAGES_PER_HPAGE(x) (1UL<<31)
> -
> #include <kvm/arm_vgic.h>
>
> struct kvm_vcpu;
> --
> 1.7.10.4
>
> _______________________________________________
> kvmarm mailing list
> kvmarm at lists.cs.columbia.edu
> https://lists.cs.columbia.edu/cucslists/listinfo/kvmarm
--
Gleb.
next prev parent reply other threads:[~2013-08-25 14:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-09 4:07 [PATCH 0/3] KVM/ARM Huge pages support Christoffer Dall
2013-08-09 4:07 ` [PATCH 1/3] KVM: Move gfn_to_index to x86 specific code Christoffer Dall
2013-08-09 4:07 ` [PATCH 2/3] KVM: ARM: Get rid of KVM_HPAGE_XXX defines Christoffer Dall
2013-08-09 4:07 ` [PATCH 3/3] KVM: ARM: Transparent huge pages and hugetlbfs support Christoffer Dall
2013-09-23 10:11 ` Marc Zyngier
2013-09-23 14:46 ` Marc Zyngier
2013-09-24 15:41 ` Steve Capper
2013-10-02 22:36 ` Christoffer Dall
2013-10-03 20:33 ` Christoffer Dall
2013-10-04 9:23 ` Marc Zyngier
2013-08-09 14:30 ` [PATCH 2/3] KVM: ARM: Get rid of KVM_HPAGE_ defines Christoffer Dall
2013-08-25 14:05 ` Gleb Natapov [this message]
2013-08-25 14:29 ` Peter Maydell
2013-08-25 14:48 ` Gleb Natapov
2013-08-25 15:18 ` Peter Maydell
2013-08-25 15:27 ` Alexander Graf
2013-08-26 10:55 ` Gleb Natapov
2013-08-26 0:46 ` Christoffer Dall
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=20130825140529.GT8218@redhat.com \
--to=gleb@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).