We register a kvm_io_bus device for the distributor and dispatch
the calls to the actual register handler at runtime.
Ideally we would register each register group directly with the
kvm_io_bus framework, but currently we run into the limit of 1000
devices pretty quickly (with GICv3), so we use this
On Tue, Apr 12, 2016 at 04:56:08PM +0100, Marc Zyngier wrote:
> On 12/04/16 13:50, Christoffer Dall wrote:
> > On Mon, Apr 11, 2016 at 11:53:21AM +0100, Andre Przywara wrote:
> >> Hi Christoffer,
> >>
> >> On 31/03/16 10:08, Christoffer Dall wrote:
> >>> Hi Andre,
> >>>
> >>> [cc'ing Paolo here for
On 12/04/16 13:50, Christoffer Dall wrote:
> On Mon, Apr 11, 2016 at 11:53:21AM +0100, Andre Przywara wrote:
>> Hi Christoffer,
>>
>> On 31/03/16 10:08, Christoffer Dall wrote:
>>> Hi Andre,
>>>
>>> [cc'ing Paolo here for his thoughts on the KVM IO bus framework]
>>>
>>> On Fri, Mar 25, 2016 at 02:
On Mon, Apr 11, 2016 at 11:53:21AM +0100, Andre Przywara wrote:
> Hi Christoffer,
>
> On 31/03/16 10:08, Christoffer Dall wrote:
> > Hi Andre,
> >
> > [cc'ing Paolo here for his thoughts on the KVM IO bus framework]
> >
> > On Fri, Mar 25, 2016 at 02:04:35AM +, Andre Przywara wrote:
> >> We
Hi Christoffer,
On 31/03/16 10:08, Christoffer Dall wrote:
> Hi Andre,
>
> [cc'ing Paolo here for his thoughts on the KVM IO bus framework]
>
> On Fri, Mar 25, 2016 at 02:04:35AM +, Andre Przywara wrote:
>> We register each register group of the distributor and redistributors
>> as separate
On Fri, Apr 01, 2016 at 01:11:06PM +0100, André Przywara wrote:
> On 31/03/16 10:08, Christoffer Dall wrote:
> > Hi Andre,
> >
> > [cc'ing Paolo here for his thoughts on the KVM IO bus framework]
> >
> > On Fri, Mar 25, 2016 at 02:04:35AM +, Andre Przywara wrote:
> >> We register each registe
On 31/03/16 10:08, Christoffer Dall wrote:
> Hi Andre,
>
> [cc'ing Paolo here for his thoughts on the KVM IO bus framework]
>
> On Fri, Mar 25, 2016 at 02:04:35AM +, Andre Przywara wrote:
>> We register each register group of the distributor and redistributors
>> as separate regions of the kv
On Thu, Mar 31, 2016 at 02:25:02PM +0200, Paolo Bonzini wrote:
>
>
> On 31/03/2016 11:09, Christoffer Dall wrote:
> >> My comments to Vladimir's bug report notwithstanding, there's still a
> >> choice here to:
> >>
> >> 1) Expand/modify the KVM IO bus framework to take an arbitrary number of
> >
On 31/03/2016 11:09, Christoffer Dall wrote:
>> My comments to Vladimir's bug report notwithstanding, there's still a
>> choice here to:
>>
>> 1) Expand/modify the KVM IO bus framework to take an arbitrary number of
>> devices
>>
>> 2) Build a KVM architectureal generic framework on top of the I
[really cc'ing Paolo this time]
On Thu, Mar 31, 2016 at 11:08 AM, Christoffer Dall
wrote:
> Hi Andre,
>
> [cc'ing Paolo here for his thoughts on the KVM IO bus framework]
>
> On Fri, Mar 25, 2016 at 02:04:35AM +, Andre Przywara wrote:
>> We register each register group of the distributor and
Hi Andre,
[cc'ing Paolo here for his thoughts on the KVM IO bus framework]
On Fri, Mar 25, 2016 at 02:04:35AM +, Andre Przywara wrote:
> We register each register group of the distributor and redistributors
> as separate regions of the kvm-io-bus framework. This way calls get
> directly hande
We register each register group of the distributor and redistributors
as separate regions of the kvm-io-bus framework. This way calls get
directly handed over to the actual handler.
This puts a lot more regions into kvm-io-bus than what we use at the
moment on other architectures, so we will probab
12 matches
Mail list logo
