On Tue, May 03, 2016 at 10:21:24AM +0200, Christoffer Dall wrote:
> On Mon, May 02, 2016 at 12:54:14PM +, Jason Cooper wrote:
> > On Thu, Apr 28, 2016 at 02:13:23PM +0100, Marc Zyngier wrote:
> > > [+ Thomas, Jason]
> > >
> > > Do you have any objection against this going through the KVM tree?
On Mon, May 02, 2016 at 12:54:14PM +, Jason Cooper wrote:
> On Thu, Apr 28, 2016 at 02:13:23PM +0100, Marc Zyngier wrote:
> > [+ Thomas, Jason]
> >
> > Do you have any objection against this going through the KVM tree? The
> > dependencies are rather intricate, and Daniel gave us his green lig
On Thu, Apr 28, 2016 at 02:13:23PM +0100, Marc Zyngier wrote:
> [+ Thomas, Jason]
>
> Do you have any objection against this going through the KVM tree? The
> dependencies are rather intricate, and Daniel gave us his green light
> already for the clocksource part.
>
> If you'd rather maintain the
[+ Thomas, Jason]
Do you have any objection against this going through the KVM tree? The
dependencies are rather intricate, and Daniel gave us his green light
already for the clocksource part.
If you'd rather maintain the usual flow, please let us know and we'll
deal with it.
Thanks,
M.
Hello,
This patch series allows KVM to work with ACPI on ARM64.
Currently, the firmware tables are parsed by the the virtual timer and virtual
GIC code in order to configure them correctly.
However the parsing of these tables is already done in the GIC and arch timer
drivers. This patch series i
5 matches
Mail list logo