From: Marcelo Tosatti <mtosatti@redhat.com>
To: Joerg Roedel <joerg.roedel@amd.com>
Cc: Avi Kivity <avi@redhat.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] Use u64 for gfn_t in KVM
Date: Fri, 2 Jul 2010 14:19:53 -0300 [thread overview]
Message-ID: <20100702171953.GD25969@amt.cnet> (raw)
In-Reply-To: <1277992812-31945-1-git-send-email-joerg.roedel@amd.com>
On Thu, Jul 01, 2010 at 04:00:10PM +0200, Joerg Roedel wrote:
> Hi, Avi, Marcelo,
>
> these two patches currently lie on the bottom of my npt-npt patch set. They
> came out of a discussion on the mailing list about the last version of the
> npt-npt patchset. These patches are independent of the rest of the patchset, so
> I post and discuss them seperatly. The changes to make gfn_t an u64 were
> larger than I expected which is another reason for the seperate post. Please
> let me know what you think about this change.
>
> Thanks,
>
> Joerg
>
> Diffstat:
>
> arch/ia64/include/asm/kvm_host.h | 1 +
> arch/powerpc/include/asm/kvm_host.h | 1 +
> arch/s390/include/asm/kvm_host.h | 3 ++-
> arch/x86/include/asm/kvm_host.h | 3 ++-
> arch/x86/kvm/mmu.c | 8 ++++----
> include/linux/kvm_types.h | 4 ++--
> virt/kvm/iommu.c | 2 +-
> virt/kvm/kvm_main.c | 10 +++++-----
> 8 files changed, 18 insertions(+), 14 deletions(-)
>
> Shortlog:
>
> Joerg Roedel (2):
> KVM: Remove unnecessary divide operations
> KVM: Use u64 for frame data types
Applied, thanks.
prev parent reply other threads:[~2010-07-02 17:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-01 14:00 [PATCH 0/2] Use u64 for gfn_t in KVM Joerg Roedel
2010-07-01 14:00 ` [PATCH 1/2] KVM: Remove unnecessary divide operations Joerg Roedel
2010-07-01 14:18 ` Avi Kivity
2010-07-01 14:00 ` [PATCH 2/2] KVM: Use u64 for frame data types Joerg Roedel
2010-07-01 14:18 ` [PATCH 0/2] Use u64 for gfn_t in KVM Avi Kivity
2010-07-02 17:19 ` Marcelo Tosatti [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=20100702171953.GD25969@amt.cnet \
--to=mtosatti@redhat.com \
--cc=avi@redhat.com \
--cc=joerg.roedel@amd.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@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