| 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
| ||
|
Message-ID: <20090625192329.GB3239@redhat.com> Date: Thu, 25 Jun 2009 22:23:29 +0300 From: "Michael S. Tsirkin" <mst@...hat.com> To: Gregory Haskins <gregory.haskins@...il.com> Cc: Gregory Haskins <ghaskins@...ell.com>, avi@...hat.com, kvm@...r.kernel.org, linux-kernel@...r.kernel.org, mtosatti@...hat.com, paulmck@...ux.vnet.ibm.com, markmc@...hat.com Subject: Re: [PATCH] kvm: pass value to in_range callback On Thu, Jun 25, 2009 at 10:49:51AM -0400, Gregory Haskins wrote: > Michael S. Tsirkin wrote: > > For write transactions, pass the value written to in_range checks so > > that we can make each iosignalfd a separate device on kvm bus. > > > > Signed-off-by: Michael S. Tsirkin <mst@...hat.com> > > --- > > > > Reposting with a subject now. Sorry. > > > > Avi, can you please merge this patch in kvm.git so that > > Gregory can use it for iosignalfd? Once bus has RCU > > we'll be able to remove in_range completely, but > > let's do it step by step. > > > > I think this patch will just make more churn for me, not less. You have > now convinced me that your io_range-less approach is better. ;) > > Lets just fix the RCU thing and do it right. Patch is under development > as we speak. > > -Greg So - let's go ahead with this one? -- 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/
Powered by blists - more mailing lists