On 06/17/2013 12:46 PM, Alexander Graf wrote:
On 06/17/2013 10:51 AM, Alexey Kardashevskiy wrote:
On 06/17/2013 06:40 PM, Alexander Graf wrote:
On 17.06.2013, at 10:34, Alexey Kardashevskiy wrote:
On 06/17/2013 06:02 PM, Alexander Graf wrote:
On 17.06.2013, at 09:55, Alexey Kardashevskiy wro
On 06/17/2013 10:51 AM, Alexey Kardashevskiy wrote:
On 06/17/2013 06:40 PM, Alexander Graf wrote:
On 17.06.2013, at 10:34, Alexey Kardashevskiy wrote:
On 06/17/2013 06:02 PM, Alexander Graf wrote:
On 17.06.2013, at 09:55, Alexey Kardashevskiy wrote:
On 06/17/2013 08:06 AM, Alexander Graf wr
On 06/17/2013 06:40 PM, Alexander Graf wrote:
>
> On 17.06.2013, at 10:34, Alexey Kardashevskiy wrote:
>
>> On 06/17/2013 06:02 PM, Alexander Graf wrote:
>>>
>>> On 17.06.2013, at 09:55, Alexey Kardashevskiy wrote:
>>>
On 06/17/2013 08:06 AM, Alexander Graf wrote:
>
> On 05.06.201
On 17.06.2013, at 10:37, Benjamin Herrenschmidt wrote:
> On Mon, 2013-06-17 at 17:55 +1000, Alexey Kardashevskiy wrote:
>> David:
>> ===
>> So, in the case of MULTITCE, that's not quite right. PR KVM can
>> emulate a PAPR system on a BookE machine, and there's no reason not to
>> allow TCE accel
On 17.06.2013, at 10:34, Alexey Kardashevskiy wrote:
> On 06/17/2013 06:02 PM, Alexander Graf wrote:
>>
>> On 17.06.2013, at 09:55, Alexey Kardashevskiy wrote:
>>
>>> On 06/17/2013 08:06 AM, Alexander Graf wrote:
On 05.06.2013, at 08:11, Alexey Kardashevskiy wrote:
> This a
On Mon, 2013-06-17 at 17:55 +1000, Alexey Kardashevskiy wrote:
> David:
> ===
> So, in the case of MULTITCE, that's not quite right. PR KVM can
> emulate a PAPR system on a BookE machine, and there's no reason not to
> allow TCE acceleration as well. We can't make it dependent on PAPR
> mode bein
On 06/17/2013 06:02 PM, Alexander Graf wrote:
>
> On 17.06.2013, at 09:55, Alexey Kardashevskiy wrote:
>
>> On 06/17/2013 08:06 AM, Alexander Graf wrote:
>>>
>>> On 05.06.2013, at 08:11, Alexey Kardashevskiy wrote:
>>>
This adds real mode handlers for the H_PUT_TCE_INDIRECT and
H_STUFF_
On 17.06.2013, at 09:55, Alexey Kardashevskiy wrote:
> On 06/17/2013 08:06 AM, Alexander Graf wrote:
>>
>> On 05.06.2013, at 08:11, Alexey Kardashevskiy wrote:
>>
>>> This adds real mode handlers for the H_PUT_TCE_INDIRECT and
>>> H_STUFF_TCE hypercalls for QEMU emulated devices such as IBMVIO
On 06/17/2013 08:06 AM, Alexander Graf wrote:
>
> On 05.06.2013, at 08:11, Alexey Kardashevskiy wrote:
>
>> This adds real mode handlers for the H_PUT_TCE_INDIRECT and
>> H_STUFF_TCE hypercalls for QEMU emulated devices such as IBMVIO
>> devices or emulated PCI. These calls allow adding multiple
On 05.06.2013, at 08:11, Alexey Kardashevskiy wrote:
> This adds real mode handlers for the H_PUT_TCE_INDIRECT and
> H_STUFF_TCE hypercalls for QEMU emulated devices such as IBMVIO
> devices or emulated PCI. These calls allow adding multiple entries
> (up to 512) into the TCE table in one call w
On Wed, 2013-06-05 at 16:11 +1000, Alexey Kardashevskiy wrote:
> This adds real mode handlers for the H_PUT_TCE_INDIRECT and
> H_STUFF_TCE hypercalls for QEMU emulated devices such as IBMVIO
> devices or emulated PCI. These calls allow adding multiple entries
> (up to 512) into the TCE table in on
On 05/27/2013 08:08 PM, Paolo Bonzini wrote:
> Il 21/05/2013 05:06, Alexey Kardashevskiy ha scritto:
>> This adds real mode handlers for the H_PUT_TCE_INDIRECT and
>> H_STUFF_TCE hypercalls for QEMU emulated devices such as virtio
>> devices or emulated PCI.
>
> Do you mean vio? virtio (without g
Il 21/05/2013 05:06, Alexey Kardashevskiy ha scritto:
> This adds real mode handlers for the H_PUT_TCE_INDIRECT and
> H_STUFF_TCE hypercalls for QEMU emulated devices such as virtio
> devices or emulated PCI.
Do you mean vio? virtio (without getting into whether that's good or
bad) will bypass th
13 matches
Mail list logo