On Mon, Jul 01, 2019 at 11:02:55AM +0200, Andrea Bolognani wrote:
> On Mon, 2019-07-01 at 09:50 +0100, Daniel P. Berrangé wrote:
> > On Mon, Jul 01, 2019 at 10:35:17AM +1000, David Gibson wrote:
> > > On Fri, Jun 14, 2019 at 01:45:24PM +0200, Andrea Bolognani wrote:
> > > > Unfortunately there's on
On Mon, 2019-07-01 at 09:50 +0100, Daniel P. Berrangé wrote:
> On Mon, Jul 01, 2019 at 10:35:17AM +1000, David Gibson wrote:
> > On Fri, Jun 14, 2019 at 01:45:24PM +0200, Andrea Bolognani wrote:
> > > Unfortunately there's one major issue with your approach: even though
> > > it's true that a spapr
On Mon, Jul 01, 2019 at 10:35:17AM +1000, David Gibson wrote:
> On Fri, Jun 14, 2019 at 01:45:24PM +0200, Andrea Bolognani wrote:
> > On Tue, 2019-06-04 at 11:38 +1000, David Gibson wrote:
> > > spapr-vio addresses are used on POWER platform qemu guests, which are
> > > based
> > > on the PAPR spe
On Fri, Jun 14, 2019 at 01:45:24PM +0200, Andrea Bolognani wrote:
> On Tue, 2019-06-04 at 11:38 +1000, David Gibson wrote:
> > spapr-vio addresses are used on POWER platform qemu guests, which are based
> > on the PAPR specification. PAPR specifies a number of virtual devices (but
> > not virtio p
On Tue, 2019-06-04 at 11:38 +1000, David Gibson wrote:
> spapr-vio addresses are used on POWER platform qemu guests, which are based
> on the PAPR specification. PAPR specifies a number of virtual devices (but
> not virtio protocol) which are addressed in an abstract namespace.
>
> Currently, lib
spapr-vio addresses are used on POWER platform qemu guests, which are based
on the PAPR specification. PAPR specifies a number of virtual devices (but
not virtio protocol) which are addressed in an abstract namespace.
Currently, libvirt encodes these addresses as 64-bit values. This is not
corre
