linux-kernel - Re: IOMMU (Calgary) patches

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 3 Aug 2006 16:25:37 -0500
From:	Jon Mason <jdmason@...ibm.com>
To:	"Duran, Leo" <leo.duran@....com>
Cc:	Muli Ben-Yehuda <muli@...ibm.com>, Andi Kleen <ak@...e.de>,
	linux-kernel@...r.kernel.org, discuss@...-64.org
Subject: Re: IOMMU (Calgary) patches

On Thu, Aug 03, 2006 at 04:10:55PM -0500, Duran, Leo wrote:
> Andi, Jon, Muli,
> 
> I'm trying to build with the latest IOMMU patches for x86_64, so, I've
> pulled down 2.6.17, and the 2.6.18-rc3 patches... But, that's obviously
> lagging behind a bit.
> 
> Is there a source tree that you guys work from?
Hey Leo,

I personally use the mercurial tree hosted on kernel.org
(http://www.kernel.org/hg/linux-2.6).  Alternatively, you can use git to
access the latest tree.

> (I'm hoping that there's a better mechanism than keeping track of
> patches as they are submitted here).

Andrew Morton is good about pulling in the IOMMU patches as soon as we
push them.  So the -mm kernel is an option.  Andi also queues up the
patches in his firstfloor repository.  So you can pull the patches from
there.

So, if you can't wait for the latest kernel and don't want to
get the latest kernel and patch it with Andi's patches on firstfloor,
then the mm kernel will be the best option.  But, the mercurial tree I
mentioned above should be sufficient.

Thanks,
Jon

> Leo Duran.
> 
> -----Original Message-----
> From: Muli Ben-Yehuda [mailto:muli@...ibm.com] 
> Sent: Thursday, August 03, 2006 2:24 AM
> To: Rolf Eike Beer
> Cc: Andrew Morton; linux-kernel@...r.kernel.org; Andi Kleen;
> discuss@...-64.org
> Subject: [discuss] Re: [PATCH] Move valid_dma_direction() from x86_64 to
> generic code
> 
> On Thu, Aug 03, 2006 at 08:25:19AM +0200, Rolf Eike Beer wrote:
> 
> > > ./arch/x86_64/kernel/pci-swiotlb.c:6:#include <asm/dma-mapping.h>
> > > ./drivers/net/fec_8xx/fec_main.c:40:#include <asm/dma-mapping.h>
> > > ./drivers/net/fs_enet/fs_enet.h:11:#include <asm/dma-mapping.h>
> > > ./include/asm-x86_64/swiotlb.h:5:#include <asm/dma-mapping.h>
> > 
> > I suspect it to be a bug anyway that every of this files ever included
> 
> > asm/dma-mapping.h.
> 
> Agreed wrt the fs_enet and fec_8xx; the swiotlb stuff I dimly recall I
> had a reason for. I'll take a look in bit to verify akpm's fix works.
> 
> > > ./include/linux/dma-mapping.h:27:#include <asm/dma-mapping.h>
> > 
> > This is perfectly valid, isn't it :)
> 
> :-)
> 
> Cheers,
> Muli
> 
> 
> 
> 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/