ut for now it is
better to just revert it. Revert attached.
>From 89736a0ee81d14439d085c8d4653bc1d86fe64d8 Mon Sep 17 00:00:00 2001
From: Joerg Roedel
Date: Mon, 6 May 2019 14:24:18 +0200
Subject: [PATCH] Revert "iommu/amd: Remove the leftover of bypass support"
This reverts commit 7
Hi Mark,
On Thu, Mar 26, 2015 at 10:58:15AM -0400, Mark Hounschell wrote:
> Sorry but CMA was still badly broken. I have a patch below that works.
In which way is it broken? What happens when you try to allocate memory
with dma_alloc_coherent?
> I've tested it with small (no CMA) and large (with
On Wed, Mar 25, 2015 at 12:36:34PM -0400, Mark Hounschell wrote:
> BTW, so far the first 2 patches are working well. I was going to
> wait until the end of the day to report but so far I have been
> unable to produce the problems I was seeing. And I am in the middle
> of some driver work so lots of
Hi again,
On Wed, Mar 25, 2015 at 02:59:37PM +0100, Joerg Roedel wrote:
> On Tue, Mar 24, 2015 at 07:57:49AM -0400, Mark Hounschell wrote:
> > I'll be happy to test it.
>
> Okay, here you go:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/joro/linux.git am
On Tue, Mar 24, 2015 at 07:57:49AM -0400, Mark Hounschell wrote:
> I'll be happy to test it.
Okay, here you go:
git://git.kernel.org/pub/scm/linux/kernel/git/joro/linux.git amd-iommu
This branch has two patches on-top of v4.0-rc5 which should fix the
issue you described here. Please let
Hi Mark,
On Tue, Mar 03, 2015 at 02:36:19PM -0500, Mark Hounschell wrote:
> It looks like this problem is NOT a bug with the SCSI aic7xxx driver
> after all. I can duplicate this BUG very easily with other hardware.
> Simply removing a driver module (whether it its self, has actually
> used any o
t;> > Ok so I don't see those DMA messages and system starts just fine. I'm
> > >> > thinking perhaps something broke after the IO mmu stuff in commit
> > >> > 3f583bc21977a608908b83d03ee2250426a5695c... could this be indirectly
> > >> > causi
Hi Eddie,
> On Tue, 2013-02-19 at 18:30 -0800, Eddie Wai wrote:
> > The code seems correct as it make sense to impose the same hardware
> > segment boundary limit on both the blk queue and the DMA code. It would
> > be an easy alternative to simply prevent the shost->dma_boundary from
> > being s
8 matches
Mail list logo
