From: Gleb Natapov <gleb@redhat.com>
To: kvm-ia64@vger.kernel.org
Subject: Re: [PATCH 0/6] Get rid of mandatory huge page defines
Date: Sun, 13 Oct 2013 09:31:29 +0000 [thread overview]
Message-ID: <20131013093129.GF15657@redhat.com> (raw)
In-Reply-To: <1380748953-7864-1-git-send-email-christoffer.dall@linaro.org>
On Sat, Oct 12, 2013 at 10:36:36AM -0700, Christoffer Dall wrote:
> On Wed, Oct 02, 2013 at 02:22:27PM -0700, Christoffer Dall wrote:
> > The current KVM code relies on a number of definitions to exist for each
> > architecture:
> > KVM_HPAGE_GFN_SHIFT
> > KVM_NR_HPAGE_SIZES
> > KVM_PAGES_PER_HPAGE
> >
> > However, these defines are only used in the gfn_to_index function, which
> > is only used in the x86 code. This series moves the gfn_to_index
> > function from the generic KVM code into the x86 world and gets rid of
> > the definitions from archiectures that don't use them. s390 actually
> > uses these values in other code, so we leave that part untouched.
> >
> > Patches based on kvm/next and available here:
> > git://git.linaro.org/people/cdall/linux-kvm-arm.git kvm-pagesize-cleanup
> >
> > Christoffer Dall (6):
> > KVM: Move gfn_to_index to x86 specific code
> > KVM: ARM: Get rid of KVM_HPAGE defines
> > KVM: arm64: Get rid of KVM_HPAGE defines
> > KVM: mips: Get rid of KVM_HPAGE defines
> > KVM: ia64: Get rid of KVM_HPAGE defines
> > KVM: PPC: Get rid of KVM_HPAGE defines
> >
>
> Any comments on this one? I'd very much like to merge huge page support
> for KVM/ARM during the next merge window and it depends on this
> series.
>
Looks fine to me, but why have you skipped s390?
--
Gleb.
next prev parent reply other threads:[~2013-10-13 9:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-02 21:22 [PATCH 0/6] Get rid of mandatory huge page defines Christoffer Dall
2013-10-12 17:36 ` Christoffer Dall
2013-10-13 9:31 ` Gleb Natapov [this message]
2013-10-13 17:41 ` Christoffer Dall
2013-10-13 17:49 ` Gleb Natapov
2013-10-13 19:29 ` Christoffer Dall
2013-10-14 7:20 ` Gleb Natapov
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=20131013093129.GF15657@redhat.com \
--to=gleb@redhat.com \
--cc=kvm-ia64@vger.kernel.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