From: Avi Kivity <avi@redhat.com>
To: Joerg Roedel <joerg.roedel@amd.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 6/7] kvm mmu: enabling 1GB pages by extending backing_size funtion
Date: Sun, 29 Mar 2009 14:51:52 +0300 [thread overview]
Message-ID: <49CF60D8.1060305@redhat.com> (raw)
In-Reply-To: <1238164319-16092-7-git-send-email-joerg.roedel@amd.com>
Joerg Roedel wrote:
> This patch enables support for 1GB pages in KVM by implementing
> the support in backing_size().
>
> @@ -490,18 +492,30 @@ static enum kvm_page_size host_page_size(struct kvm *kvm, gfn_t gfn)
> static enum kvm_page_size backing_size(struct kvm_vcpu *vcpu, gfn_t gfn)
> {
> struct kvm_memory_slot *slot;
> -
> - if (has_wrprotected_page(vcpu->kvm, gfn))
> - return KVM_PAGE_SIZE_4k;
> -
> - if (host_page_size(vcpu->kvm, gfn) < KVM_PAGE_SIZE_2M)
> - return KVM_PAGE_SIZE_4k;
> + enum kvm_page_size host_size, ret;
>
> slot = gfn_to_memslot(vcpu->kvm, gfn);
> if (slot && slot->dirty_bitmap)
> return KVM_PAGE_SIZE_4k;
>
> - return KVM_PAGE_SIZE_2M;
> + host_size = host_page_size(vcpu->kvm, gfn);
> +
> + switch (host_size) {
> + case KVM_PAGE_SIZE_1G:
> + if (!has_wrprotected_largepage(vcpu->kvm, gfn)) {
> + ret = KVM_PAGE_SIZE_1G;
> + break;
> + }
>
What if there's a wrprotected_page in there?
> + case KVM_PAGE_SIZE_2M:
> + if (!has_wrprotected_page(vcpu->kvm, gfn)) {
> + ret = KVM_PAGE_SIZE_2M;
> + break;
> + }
> + default:
> + ret = KVM_PAGE_SIZE_4k;
> + }
> +
> + return ret;
> }
>
> /*
>
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-03-29 11:52 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-27 14:31 [PATCH 0/7] Support for GB pages in KVM Joerg Roedel
2009-03-27 14:31 ` [PATCH 1/7] hugetlb: export vma_kernel_pagesize to modules Joerg Roedel
2009-03-27 14:31 ` [PATCH 2/7] kvm mmu: infrastructure changes for multiple huge page support Joerg Roedel
2009-03-29 11:38 ` Avi Kivity
2009-03-27 14:31 ` [PATCH 3/7] kvm mmu: add page size parameter to rmap_remove Joerg Roedel
2009-03-27 14:31 ` [PATCH 4/7] kvm mmu: implement necessary data structures for second huge page accounting Joerg Roedel
2009-03-29 11:45 ` Avi Kivity
2009-03-29 13:03 ` Joerg Roedel
2009-03-29 13:15 ` Avi Kivity
2009-03-29 13:32 ` Joerg Roedel
2009-03-29 13:26 ` Avi Kivity
2009-03-29 13:37 ` Avi Kivity
2009-03-27 14:31 ` [PATCH 5/7] kvm mmu: add support for 1GB pages to direct mapping paths Joerg Roedel
2009-03-29 11:49 ` Avi Kivity
2009-03-27 14:31 ` [PATCH 6/7] kvm mmu: enabling 1GB pages by extending backing_size funtion Joerg Roedel
2009-03-29 11:51 ` Avi Kivity [this message]
2009-03-27 14:31 ` [PATCH 7/7] kvm x86: report 1GB page support to userspace Joerg Roedel
2009-03-29 11:54 ` Avi Kivity
2009-03-29 12:45 ` Joerg Roedel
2009-03-29 12:49 ` Avi Kivity
2009-03-29 12:54 ` Joerg Roedel
2009-03-29 13:00 ` Avi Kivity
2009-03-28 21:40 ` [PATCH 0/7] Support for GB pages in KVM Marcelo Tosatti
2009-03-28 21:49 ` Joerg Roedel
2009-03-29 12:03 ` Avi Kivity
2009-03-29 12:47 ` Joerg Roedel
2009-03-29 12:01 ` Avi Kivity
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=49CF60D8.1060305@redhat.com \
--to=avi@redhat.com \
--cc=joerg.roedel@amd.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.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.