Hi, Joerg,
The problem you describe here should also be fixed by this (simpler)
patch. Can you test this please?
The running result of this patch is correct.
My opinion is we should avoid modifying the original data
early_ioapic_map[i].devid and devid from IVHD since they are original data
Hi Will,
On Mon, Sep 08, 2014 at 05:51:36PM +0100, Will Deacon wrote:
On Fri, Sep 05, 2014 at 11:52:56AM +0100, Joerg Roedel wrote:
switch (cap) {
case IOMMU_CAP_CACHE_COHERENCY:
- return features ARM_SMMU_FEAT_COHERENT_WALK;
+ /*
+* Use
Hi Will,
On 09/08/2014 01:31 PM, Will Deacon wrote:
On Fri, Sep 05, 2014 at 04:37:41PM +0100, Grygorii Strashko wrote:
On 09/02/2014 08:56 PM, Will Deacon wrote:
set_arch_dma_coherent_ops is called from of_dma_configure in order to
swizzle the architectural dma-mapping functions over to a
From: Joerg Roedel jroe...@suse.de
Add calls to the new mmu_notifier_invalidate_range()
function to all places if the VMM that need it.
Reviewed-by: Andrea Arcangeli aarca...@redhat.com
Reviewed-by: Jérôme Glisse jgli...@redhat.com
Signed-off-by: Joerg Roedel jroe...@suse.de
---
From: Joerg Roedel jroe...@suse.de
This notifier closes two important gaps with the current
invalidate_range_start()/end() notifiers. The _start() part
is called when all pages are still mapped while the _end()
notifier is called when all pages are potentially unmapped
and already freed.
This
Changes V2-V3:
* Rebased to v3.17-rc4
* Fixed compile error because pmdp_get_and_clear_notify was
missing
Changes V1-V2:
* Rebase to v3.16-rc7
* Added call of -invalidate_range to
__mmu_notifier_invalidate_end() so that the subsystem
doesn't need to register an -invalidate_end()
The OMAP IOMMU driver supports both the OMAP1 and OMAP2+ IOMMU variants
by splitting the driver into a core module and a thin arch-specific
operations module.
(In practice only the OMAP2+ module omap-iommu2 is implemented, but
let's not denigrate the effort.)
The arch-specific operations module
Hello,
Those two patches clean up the OMAP IOMMU driver. Please see individual commit
messages for more information.
Laurent Pinchart (2):
iommu/omap: Reverse dependency between omap-iommu and omap-iommu2
iommu/omap: Remove omap_iommu unused owner field
drivers/iommu/omap-iommu-debug.c |
Hi Laurent,
On 09/09/2014 10:45 AM, Laurent Pinchart wrote:
The OMAP IOMMU driver supports both the OMAP1 and OMAP2+ IOMMU variants
by splitting the driver into a core module and a thin arch-specific
operations module.
(In practice only the OMAP2+ module omap-iommu2 is implemented, but
Hi Laurent,
On 09/09/2014 10:45 AM, Laurent Pinchart wrote:
The owner field is never set. Remove it.
Thanks, this seems to have been dead code since the days OMAP IOMMU has
been converted from building as modules to built-in as part of the IOMMU
API adoption. So,
Acked-by: Suman Anna
The previous change (iommu/vt-d: Don't store SIRTP request) to this area
caused a crash in our simulator. In particular is seems that by the time a
UART interrupt is sent through the system, we don't see interrupt remapping
to be enabled. So the interrupt does not get translated to a logical
Hi Alex,
I've attached what you've requested after I reenabled iommu.
On Fri, Sep 5, 2014 at 9:01 PM, Alex Williamson
alex.william...@redhat.com wrote:
On Fri, 2014-09-05 at 20:00 -0700, Jason Newton wrote:
Hi,
I have an AR9462 connected over minipcie, it came with the ASRock
FM2A88x-itx
12 matches
Mail list logo
