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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Wed, 17 Dec 2014 11:50:00 +0100
From:	Joerg Roedel <jroedel@...e.de>
To:	Paolo Bonzini <pbonzini@...hat.com>
Cc:	"Chen, Tiejun" <tiejun.chen@...el.com>,
	Joerg Roedel <joro@...tes.org>, Gleb Natapov <gleb@...nel.org>,
	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 11:46:24AM +0100, Paolo Bonzini wrote:
> 
> 
> On 17/12/2014 11:35, Joerg Roedel wrote:
> >> > 
> >> > 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?
> 
> kvm/master in the -rc period, kvm/next during the merge window and for
> the next release.  But it's not a problem, I can sort it out.

Great, thanks Paolo. So I will base my future patches on kvm/next.


	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/