On Tue, Jul 18, 2017 at 01:44:34PM +0100, Peter Maydell wrote:
> On 18 July 2017 at 13:38, Andrew Jones wrote:
> > On Mon, Jul 10, 2017 at 04:27:35PM +0100, Peter Maydell wrote:
> >> On 1 July 2017 at 17:47, Andrew Jones wrote:
> >> > When adding a PMU with a userspace irqchip we only do the INIT
On 18 July 2017 at 13:38, Andrew Jones wrote:
> On Mon, Jul 10, 2017 at 04:27:35PM +0100, Peter Maydell wrote:
>> On 1 July 2017 at 17:47, Andrew Jones wrote:
>> > When adding a PMU with a userspace irqchip we only do the INIT
>> > stage of the device creation.
>>
>> Can you explain why? My assum
On Mon, Jul 10, 2017 at 04:27:35PM +0100, Peter Maydell wrote:
> On 1 July 2017 at 17:47, Andrew Jones wrote:
> > When adding a PMU with a userspace irqchip we only do the INIT
> > stage of the device creation.
>
> Can you explain why? My assumption would be that either
> (a) we don't need the ke
On 1 July 2017 at 17:47, Andrew Jones wrote:
> When adding a PMU with a userspace irqchip we only do the INIT
> stage of the device creation.
Can you explain why? My assumption would be that either
(a) we don't need the kernel's PMU, in which case don't
create it at all, or
(b) we do need the ker
When adding a PMU with a userspace irqchip we only do the INIT
stage of the device creation.
Signed-off-by: Andrew Jones
---
hw/arm/virt.c| 10 --
target/arm/kvm32.c | 6 ++
target/arm/kvm64.c | 52 +---
target/arm/kvm_arm.
