From: Paolo Bonzini <pbonzini@redhat.com>
To: James Hogan <james.hogan@imgtec.com>
Cc: John Crispin <john@phrozen.org>,
Ralf Baechle <ralf@linux-mips.org>,
linux-mips@linux-mips.org, Gleb Natapov <gleb@redhat.com>,
kvm@vger.kernel.org, Markos Chandras <markos.chandras@imgtec.com>,
Sanjay Lal <sanjayl@kymasys.com>
Subject: Re: [PATCH 0/2] MIPS: KVM: fixes for KVM on ProAptiv cores
Date: Wed, 15 Jan 2014 12:09:19 +0100 [thread overview]
Message-ID: <52D66C5F.5030509@redhat.com> (raw)
In-Reply-To: <1389780682-32638-1-git-send-email-james.hogan@imgtec.com>
Il 15/01/2014 11:11, James Hogan ha scritto:
> ProAptiv support includes support for EHINV (TLB invalidation) and FTLB
> (large fixed page size TLBs), both of which cause problems when combined
> with KVM. These two patches fix those problems.
>
> These are based on John Crispin's mips-next-3.14 branch where ProAptiv
> support is applied. Please consider applying these for v3.14 too.
>
> Cc: Ralf Baechle <ralf@linux-mips.org>
> Cc: linux-mips@linux-mips.org
> Cc: Gleb Natapov <gleb@redhat.com>
> Cc: Paolo Bonzini <pbonzini@redhat.com>
> Cc: kvm@vger.kernel.org
> Cc: Markos Chandras <markos.chandras@imgtec.com>
> Cc: Sanjay Lal <sanjayl@kymasys.com>
>
> James Hogan (2):
> MIPS: KVM: use common EHINV aware UNIQUE_ENTRYHI
> MIPS: KVM: remove shadow_tlb code
>
> arch/mips/include/asm/kvm_host.h | 7 --
> arch/mips/kvm/kvm_mips.c | 1 -
> arch/mips/kvm/kvm_tlb.c | 134 +--------------------------------------
> 3 files changed, 1 insertion(+), 141 deletions(-)
>
Acked-by: Paolo Bonzini <pbonzini@redhat.com>
prev parent reply other threads:[~2014-01-15 11:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-15 10:11 [PATCH 0/2] MIPS: KVM: fixes for KVM on ProAptiv cores James Hogan
2014-01-15 10:11 ` [PATCH 1/2] MIPS: KVM: use common EHINV aware UNIQUE_ENTRYHI James Hogan
2014-01-15 10:16 ` Markos Chandras
2014-01-15 10:11 ` [PATCH 2/2] MIPS: KVM: remove shadow_tlb code James Hogan
2014-01-15 11:09 ` Paolo Bonzini [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=52D66C5F.5030509@redhat.com \
--to=pbonzini@redhat.com \
--cc=gleb@redhat.com \
--cc=james.hogan@imgtec.com \
--cc=john@phrozen.org \
--cc=kvm@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=markos.chandras@imgtec.com \
--cc=ralf@linux-mips.org \
--cc=sanjayl@kymasys.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 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).