On Tue, Jun 27, 2017 at 03:59:51PM +0200, Andrew Jones wrote:
> On Tue, Jun 27, 2017 at 03:00:10PM +0200, Alexander Graf wrote:
> > > > +/* XXX PMU IRQ is missing */
> > >
> > > So I was wondering why you chose not to wire up the PMU in order to finish
> >
> > Because the PMU IRQ is only
On Tue, Jun 27, 2017 at 03:00:10PM +0200, Alexander Graf wrote:
> > > +/* XXX PMU IRQ is missing */
> >
> > So I was wondering why you chose not to wire up the PMU in order to finish
>
> Because the PMU IRQ is only available from the machine file, so it'll need
> some more plumbing to get
On 27.06.17 14:37, Andrew Jones wrote:
On Mon, Jun 26, 2017 at 11:30:56PM +0200, Alexander Graf wrote:
When running with KVM enabled, you can choose between emulating the
gic in kernel or user space. If the kernel supports in-kernel virtualization
of the interrupt controller, it will default t
On Mon, Jun 26, 2017 at 11:30:56PM +0200, Alexander Graf wrote:
> When running with KVM enabled, you can choose between emulating the
> gic in kernel or user space. If the kernel supports in-kernel virtualization
> of the interrupt controller, it will default to that. If not, if will
> default to u
When running with KVM enabled, you can choose between emulating the
gic in kernel or user space. If the kernel supports in-kernel virtualization
of the interrupt controller, it will default to that. If not, if will
default to user space emulation.
Unfortunately when running in user mode gic emulat
