linux-kernel - Re: [PATCH] kvm: iommu: Add cond_resched to legacy device assignment code

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: <20141217103500.GA9373@suse.de>
Date:	Wed, 17 Dec 2014 11:35:00 +0100
From:	Joerg Roedel <jroedel@...e.de>
To:	"Chen, Tiejun" <tiejun.chen@...el.com>
Cc:	Joerg Roedel <joro@...tes.org>, Gleb Natapov <gleb@...nel.org>,
	Paolo Bonzini <pbonzini@...hat.com>, kvm@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] kvm: iommu: Add cond_resched to legacy device assignment
 code

On Wed, Dec 17, 2014 at 09:38:57AM +0800, Chen, Tiejun wrote:
> On 2014/12/16 23:47, Joerg Roedel wrote:
> >diff --git a/virt/kvm/iommu.c b/virt/kvm/iommu.c
> >index c1e6ae9..ac427e8 100644
> >--- a/virt/kvm/iommu.c
> >+++ b/virt/kvm/iommu.c
> 
> This file is already gone after one latest commit c274e03af705,
> "kvm: x86: move assigned-dev.c and iommu.c to arch/x86/" is
> introduced, so you need to pull your tree firstly :)

Hmm, I based the patch on kvm/master, where the file is still present.
What is the branch to base kvm patches on these days?


	Joerg

--
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/