Re: [Qemu-devel] [PATCH 3/3] pseries: Use Book3S-HV TCE acceleration capabilities

2011-09-29 Thread David Gibson
On Thu, Sep 29, 2011 at 03:29:59PM +0200, Alexander Graf wrote: > On 29.09.2011, at 08:45, David Gibson wrote: [snip] > > +int kvmppc_remove_spapr_tce(void *table, int fd, uint32_t window_size) > > Hrm. Is this ever called somewhere? Not yet. It will be needed when we refactor the TCE bypass sup

Re: [Qemu-devel] [PATCH 3/3] pseries: Use Book3S-HV TCE acceleration capabilities

2011-09-29 Thread Alexander Graf
On 29.09.2011, at 08:45, David Gibson wrote: > The pseries machine of qemu implements the TCE mechanism used as a > virtual IOMMU for the PAPR defined virtual IO devices. Because the > PAPR spec only defines a small DMA address space, the guest VIO > drivers need to update TCE mappings very freq

Re: [Qemu-devel] [PATCH 3/3] pseries: Use Book3S-HV TCE acceleration capabilities

2011-09-29 Thread Jan Kiszka
On 2011-09-29 08:45, David Gibson wrote: > The pseries machine of qemu implements the TCE mechanism used as a > virtual IOMMU for the PAPR defined virtual IO devices. Because the > PAPR spec only defines a small DMA address space, the guest VIO > drivers need to update TCE mappings very frequently

[Qemu-devel] [PATCH 3/3] pseries: Use Book3S-HV TCE acceleration capabilities

2011-09-29 Thread David Gibson
The pseries machine of qemu implements the TCE mechanism used as a virtual IOMMU for the PAPR defined virtual IO devices. Because the PAPR spec only defines a small DMA address space, the guest VIO drivers need to update TCE mappings very frequently - the virtual network device is particularly bad