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
| ||
|
Date: Thu, 22 Jul 2021 15:16:17 +0200 From: Greg KH <gregkh@...uxfoundation.org> To: "Wang, Zhi A" <zhi.a.wang@...el.com> Cc: Christoph Hellwig <hch@....de>, Jani Nikula <jani.nikula@...ux.intel.com>, Joonas Lahtinen <joonas.lahtinen@...ux.intel.com>, "Vivi, Rodrigo" <rodrigo.vivi@...el.com>, Zhenyu Wang <zhenyuw@...ux.intel.com>, "intel-gfx@...ts.freedesktop.org" <intel-gfx@...ts.freedesktop.org>, "intel-gvt-dev@...ts.freedesktop.org" <intel-gvt-dev@...ts.freedesktop.org>, "dri-devel@...ts.freedesktop.org" <dri-devel@...ts.freedesktop.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org> Subject: Re: refactor the i915 GVT support On Thu, Jul 22, 2021 at 10:49:47AM +0000, Wang, Zhi A wrote: > But it's hard for some customers to contribute their own "hypervisor" > module to the upstream Linux kernel. What prevents them from doing this? We will take any code that meets our standards, what format is this external code in? > I am thinking what would be a > better solution here? The MPT layer in the kernel helps a lot for > customers, but only one open-source "hypervisor" module is there in > the kernel. That can confuse people which don't know the story. One > thing I was thinking is to put a document about the background and > more description in the MPT headers. So it won't confuse more people. If no one is using it in the kernel, it needs to be removed. No abstractions should be added that are not required by the in-tree code. So this series should be accepted, _or_ the external code needs to be submitted for inclusion. thanks, greg k-h
Powered by blists - more mailing lists