linux-kernel - Re: [PATCH] virt: IRQ bypass manager

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]

Message-ID: <1436812644.1391.375.camel@redhat.com>
Date:	Mon, 13 Jul 2015 12:37:24 -0600
From:	Alex Williamson <alex.williamson@...hat.com>
To:	Paolo Bonzini <pbonzini@...hat.com>
Cc:	linux-kernel@...r.kernel.org, kvm@...r.kernel.org,
	eric.auger@...com, eric.auger@...aro.org, joro@...tes.org,
	avi.kivity@...il.com, feng.wu@...el.com
Subject: Re: [PATCH] virt: IRQ bypass manager

On Fri, 2015-07-10 at 23:09 +0200, Paolo Bonzini wrote:
> 
> On 10/07/2015 19:52, Alex Williamson wrote:
> > Perhaps if a second consumer comes along that would be justification for
> > tying it elsewhere in the build system.  ARM will obviously need to do
> > similar.  Are there better options?
> > 
> > Also, there's no maintainer for the top level virt/ directory.  Paolo,
> > would you feel comfortable taking this, maybe with some additional acks?
> 
> That's okay; alternatively, we can share it since after all you wrote
> most of it.

Sure.  Actually my wording was confusing, I was actually just suggesting
the patch be merged through the KVM tree since I think the consumer code
is going to be significantly bulkier than the producer code.  I can
certainly add a MAINTAINERS entry for virt/lib/ that we can share if you
like.  Thanks,

Alex


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