-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 02/05/2013 08:28, David Gibson ha scritto:
> Well, we're talking here about the *target* address space of the
> iommu. So that's address_space_memory for us too. In fact I
> don't know of any realistic cases where the target AS won't be
> addres
On Thu, May 02, 2013 at 07:24:54AM +0200, Paolo Bonzini wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Il 02/05/2013 05:05, David Gibson ha scritto:
> >>> I think the problem is that we do not have reference counting,
> >>> and this makes it simpler to manage the lifetime. It can be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 02/05/2013 05:05, David Gibson ha scritto:
>>> I think the problem is that we do not have reference counting,
>>> and this makes it simpler to manage the lifetime. It can be
>>> changed later.
> I don't really follow this logic. In the existing ca
On Wed, May 01, 2013 at 06:10:47PM +0200, Paolo Bonzini wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Il 01/05/2013 06:35, David Gibson ha scritto:
> >> From: Avi Kivity
> >>
> >> Add a new memory region type that translates addresses it is
> >> given, then forwards them to a targ
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 01/05/2013 06:35, David Gibson ha scritto:
>> From: Avi Kivity
>>
>> Add a new memory region type that translates addresses it is
>> given, then forwards them to a target address space. This is
>> similar to an alias, except that the mapping is m
> From: Avi Kivity
>
> Add a new memory region type that translates addresses it is given,
> then forwards them to a target address space. This is similar to
> an alias, except that the mapping is more flexible than a linear
> translation and trucation, and also less efficient since the
> transl
