[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [RFC v1 3/7] memory: iommu support
From: |
Avi Kivity |
Subject: |
Re: [Qemu-devel] [RFC v1 3/7] memory: iommu support |
Date: |
Thu, 11 Oct 2012 15:57:01 +0200 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120911 Thunderbird/15.0.1 |
On 10/11/2012 03:54 PM, Paolo Bonzini wrote:
> Il 11/10/2012 15:45, Avi Kivity ha scritto:
>>>> >> +struct MemoryRegionIOMMUOps {
>>>> >> + /* Returns a TLB entry that contains a given address. */
>>>> >> + IOMMUTLBEntry (*translate)(MemoryRegion *iommu, target_phys_addr_t
>>>> >> addr,
>>>> >> + bool is_write);
>>>> >> +};
>>> >
>>> > Do map/unmap still make sense in this model? Ben & David, what were
>>> > your plans there?
>>> >
>> Map/unmap is supported via address_space_map(), which calls
>> ->translate(). I don't see how a lower-level map/unmap helps, unless
>> the hardware supplies such a function.
>
> Yep, it's just the map/unmap callbacks that are not supported anymore,
> but nobody uses that feature of DMAContext yet.
What do those callbacks it even mean?
--
error compiling committee.c: too many arguments to function
Re: [Qemu-devel] [RFC v1 3/7] memory: iommu support, Avi Kivity, 2012/10/11
[Qemu-devel] [RFC v1 5/7] i440fx: add an iommu, Avi Kivity, 2012/10/11
[Qemu-devel] [RFC v1 6/7] vfio: abort if an emulated iommu is used, Avi Kivity, 2012/10/11
[Qemu-devel] [RFC v1 7/7] vhost: abort if an emulated iommu is used, Avi Kivity, 2012/10/11