linux-kernel - Re: [PATCH 0/2] x86: per-device dma_mapping

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 for Android: free password hash cracker in your pocket

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

Message-Id: <20080515181619R.tomof@acm.org>
Date:	Thu, 15 May 2008 18:16:19 +0900
From:	FUJITA Tomonori <fujita.tomonori@....ntt.co.jp>
To:	andi@...stfloor.org
Cc:	fujita.tomonori@....ntt.co.jp, linux-kernel@...r.kernel.org,
	akpm@...ux-foundation.org, muli@...ibm.com, alexisb@...ibm.com
Subject: Re: [PATCH 0/2] x86: per-device dma_mapping_ops

On Thu, 15 May 2008 11:01:09 +0200
Andi Kleen <andi@...stfloor.org> wrote:

> FUJITA Tomonori <fujita.tomonori@....ntt.co.jp> writes:
> 
> > This patchset adds per-device dma_mapping_ops support for
> > CONFIG_X86_64 like POWER architecture does. This change enables us to
> > cleanly fix the Calgary IOMMU issue that some devices are not behind
> > the IOMMU [1]. It also would be helpful to handle KVM PCI passthrough.
> 
> This makes it basically impossible to do stack ops, which some 
> people have been doing.

Seems that I misunderstand what those people want.

What those people want to do and how the stack ops achieve it? Or can
you tell me where their patches are?
--
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/