linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Mihai Caraman <mihai.caraman@freescale.com>
To: <kvm-ppc@vger.kernel.org>
Cc: Mihai Caraman <mihai.caraman@freescale.com>,
	linuxppc-dev@lists.ozlabs.org, kvm@vger.kernel.org
Subject: [PATCH 0/6] KVM: PPC: Book3E: AltiVec support
Date: Wed, 3 Jul 2013 15:42:33 +0300	[thread overview]
Message-ID: <1372855359-13452-1-git-send-email-mihai.caraman@freescale.com> (raw)

Add KVM Book3E AltiVec support and enable e6500 core.

Mihai Caraman (6):
  KVM: PPC: Book3E: Use common defines for SPE/FP/AltiVec int numbers
  KVM: PPC: Book3E: Refactor SPE/FP exit handling
  KVM: PPC: Book3E: Increase FPU laziness
  KVM: PPC: Book3E: Add AltiVec support
  KVM: PPC: Book3E: Add ONE_REG AltiVec support
  KVM: PPC: Book3E: Enable e6500 core

 arch/powerpc/kvm/booke.c              |  211 +++++++++++++++++++++++++++------
 arch/powerpc/kvm/booke.h              |    5 +-
 arch/powerpc/kvm/bookehv_interrupts.S |    8 +-
 arch/powerpc/kvm/e500.c               |   10 +-
 arch/powerpc/kvm/e500_emulate.c       |    8 +-
 arch/powerpc/kvm/e500mc.c             |   12 ++-
 6 files changed, 201 insertions(+), 53 deletions(-)

-- 
1.7.3.4

             reply	other threads:[~2013-07-03 12:44 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-03 12:42 Mihai Caraman [this message]
2013-07-03 12:42 ` [PATCH 1/6] KVM: PPC: Book3E: Use common defines for SPE/FP/AltiVec int numbers Mihai Caraman
2013-07-03 12:42 ` [PATCH 2/6] KVM: PPC: Book3E: Refactor SPE/FP exit handling Mihai Caraman
2013-07-03 13:30   ` Alexander Graf
2013-07-03 13:53     ` Caraman Mihai Claudiu-B02008
2013-07-03 15:13       ` Alexander Graf
2013-07-03 18:28         ` Scott Wood
2013-07-03 18:42           ` Alexander Graf
2013-07-03 18:44             ` Scott Wood
2013-07-03 12:42 ` [PATCH 3/6] KVM: PPC: Book3E: Increase FPU laziness Mihai Caraman
2013-07-03 13:45   ` Alexander Graf
2013-07-03 13:55     ` Caraman Mihai Claudiu-B02008
2013-07-03 15:11       ` Alexander Graf
2013-07-03 15:41         ` Caraman Mihai Claudiu-B02008
2013-07-03 16:59           ` Alexander Graf
2013-07-03 17:17             ` Scott Wood
2013-07-03 17:22               ` Alexander Graf
2013-07-03 17:07         ` Scott Wood
2013-07-03 17:08           ` Alexander Graf
2013-07-03 17:18   ` Scott Wood
2013-07-03 17:23     ` Alexander Graf
2013-07-03 17:44       ` Scott Wood
2013-07-03 18:39         ` Alexander Graf
2013-07-03 18:37   ` Scott Wood
2013-07-03 18:40     ` Alexander Graf
2013-07-04  6:50       ` Caraman Mihai Claudiu-B02008
2013-07-03 12:42 ` [PATCH 4/6] KVM: PPC: Book3E: Add AltiVec support Mihai Caraman
2013-07-03 15:17   ` Alexander Graf
2013-07-03 16:09     ` Caraman Mihai Claudiu-B02008
2013-07-03 16:43       ` Alexander Graf
2013-07-03 16:49         ` Caraman Mihai Claudiu-B02008
2013-07-03 17:07           ` Alexander Graf
2013-07-03 18:36             ` Scott Wood
2013-07-03 18:45               ` Alexander Graf
2013-07-03 18:38   ` Scott Wood
2013-07-03 12:42 ` [PATCH 5/6] KVM: PPC: Book3E: Add ONE_REG " Mihai Caraman
2013-07-03 12:42 ` [PATCH 6/6] KVM: PPC: Book3E: Enable e6500 core Mihai Caraman

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=1372855359-13452-1-git-send-email-mihai.caraman@freescale.com \
    --to=mihai.caraman@freescale.com \
    --cc=kvm-ppc@vger.kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).