[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130614111223.GB15775@linux-mips.org>
Date: Fri, 14 Jun 2013 13:12:23 +0200
From: Ralf Baechle <ralf@...ux-mips.org>
To: David Daney <ddaney.cavm@...il.com>
Cc: linux-mips@...ux-mips.org, kvm@...r.kernel.org,
Sanjay Lal <sanjayl@...asys.com>, linux-kernel@...r.kernel.org,
David Daney <david.daney@...ium.com>
Subject: Re: [PATCH 00/31] KVM/MIPS: Implement hardware virtualization via
the MIPS-VZ extensions.
On Fri, Jun 07, 2013 at 04:03:04PM -0700, David Daney wrote:
> Subject: [PATCH 00/31] KVM/MIPS: Implement hardware virtualization via the
> MIPS-VZ extensions.
>
> From: David Daney <david.daney@...ium.com>
>
> These patches take a somewhat different approach to MIPS
> virtualization via the MIPS-VZ extensions than the patches previously
> sent by Sanjay Lal.
>
> Several facts about the code:
>
> o Existing exception handlers are modified to hook in to KVM instead
> of intercepting all exceptions via the EBase register, and then
> chaining to real exception handlers.
>
> o Able to boot 64-bit SMP guests that use the FPU (I have booted 4-way
> SMP 64-bit MIPS/Linux).
>
> o Additional overhead on every exception even when *no* vCPU is running.
>
> o Lower interrupt overhead, than the EBase interception method, when
> vCPU *is* running.
>
> o This code is somewhat smaller than the existing trap/emulate
> implementation (about 2100 lines vs. about 5300 lines)
>
> o Currently probably only usable on the OCTEON III CPU model, as some
> MIPS-VZ implementation-defined behaviors were assumed to have the
> OCTEON III behavior.
>
> Note: I think Ralf already has the 17/31 (MIPS: Quit exposing Kconfig
> symbols in uapi headers.) queued, but I also include it here.
Yes; as the references to CONFIG_* symbols in UAPI were a bug, I've
already merged this patch for 3.10 as 8f657933a3c2086d4731350c98f91a990783c0d3
[MIPS: Quit exposing Kconfig symbols in uapi headers.]
Ralf
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists