public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Joerg Roedel <joerg.roedel@amd.com>
Cc: Marcelo Tosatti <marcelo@kvack.org>,
	linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [PATCH 0/7 v5] KVM: support for 1gb pages
Date: Wed, 29 Jul 2009 13:00:49 +0300	[thread overview]
Message-ID: <4A701DD1.7000300@redhat.com> (raw)
In-Reply-To: <1248705048-22607-1-git-send-email-joerg.roedel@amd.com>

On 07/27/2009 05:30 PM, Joerg Roedel wrote:
> Hello,
>
> this is the latest version of the changes to KVM MMU code to support 1gb
> pages.  Pages with a size of 1gb are a feature of all Fam10h AMD CPUs
> and this patch set makes them available for guests and allows to map the
> nested page table with 1gb pages.
>    

Applied, thanks.

-- 
error compiling committee.c: too many arguments to function


      parent reply	other threads:[~2009-07-29  9:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-27 14:30 [PATCH 0/7 v5] KVM: support for 1gb pages Joerg Roedel
2009-07-27 14:30 ` [PATCH 1/7] kvm/mmu: make rmap code aware of mapping levels Joerg Roedel
2009-07-27 14:30 ` [PATCH 2/7] kvm/mmu: rename is_largepage_backed to mapping_level Joerg Roedel
2009-07-27 14:30 ` [PATCH 3/7] kvm/mmu: make direct mapping paths aware of mapping levels Joerg Roedel
2009-07-27 14:30 ` [PATCH 4/7] kvm/mmu: make page walker " Joerg Roedel
2009-07-27 14:30 ` [PATCH 5/7] kvm/mmu: shadow support for 1gb pages Joerg Roedel
2009-07-27 14:30 ` [PATCH 6/7] kvm/mmu: enable gbpages by increasing nr of pagesizes Joerg Roedel
2009-07-27 14:35   ` (kein Betreff) Jens Regel
2009-07-27 14:30 ` [PATCH 7/7] kvm x86: report 1GB page support to userspace Joerg Roedel
2009-07-29 10:00 ` Avi Kivity [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=4A701DD1.7000300@redhat.com \
    --to=avi@redhat.com \
    --cc=joerg.roedel@amd.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@kvack.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