Received: by 2002:a05:6a10:1287:0:0:0:0 with SMTP id d7csp531097pxv; Thu, 22 Jul 2021 06:17:22 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxZCf0AgGgTkgD4MkpdLpvwVq+EBoEdvbwbfMH409igjPEPQT0kVQL7tM1FDMixnwjPx+Yg X-Received: by 2002:a5e:c803:: with SMTP id y3mr30035736iol.107.1626959842262; Thu, 22 Jul 2021 06:17:22 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1626959842; cv=none; d=google.com; s=arc-20160816; b=JQ5Ehly1/ttR8MwdAhDBO8Y/LNgE9cCLNaEzgq6XGDb+erkNQedQpxDRFjCzt8j0hJ y4zVKeimcQWs3H6MS6g/Zl0Fn68cPORhTzPlqSA3I2fiJ14ZwT5gCaLw6y/l231Ncju4 CY8cyQFAtIkl6SKjblLe1UoMfmSiRQJZb30PYq7Q4ouyo8b0QhxRTby3aPHzxzd8fwTx +dAuYGfeZc4RxJ538V0GVwA1TogGUw6HCN0dAwRy6nGRZdaL+MKWVAJaGu+9EopTY87a 4cEJzWkQdU92OQoEJPvaegVcSqzrpwWXHY4vM6ZVhrWH4JKHG870WghchWnM/uzFTv8M HXAQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=3OXzOA9O0I4YDhpljAZMvm83GprEk3kQ6qEp5nWjxCM=; b=r0eEgECHw6RR+RsIr1gn2568ltDjG4hPj77uAkbLmc4lk2EWOSPjdezrHNzJKHmVwW GHAtoMNKektvPImLf5O0JzRQf9lmGGCuDTou0HZFtAkgGixeo14eH2RvT/cwHG/rhTsP AiFGDyQQf+J7PwMeXb8QB1JyskXdqKAxHMk7Lc+OpMvf6bgODTbHPKLDKdfftUuTCe1H 9OUNym2E5FXsZZVTh2N147o7qAUjwF92rzWTKeCkDHdVtkluNgm19btxBzzz/cM7/bCW HSjrA89hLdSkS71CFFc+CgdhYbF1G/av6VgWahNAyjBsho8ehmSvyx9YcAjedTC1YS2E w8Zg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=twohJJ8s; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id w11si23795396ilo.1.2021.07.22.06.17.10; Thu, 22 Jul 2021 06:17:22 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=twohJJ8s; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231939AbhGVMfr (ORCPT + 99 others); Thu, 22 Jul 2021 08:35:47 -0400 Received: from mail.kernel.org ([198.145.29.99]:39936 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230418AbhGVMfq (ORCPT ); Thu, 22 Jul 2021 08:35:46 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id 3188261003; Thu, 22 Jul 2021 13:16:19 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1626959780; bh=CrztZNaKVjON/d/4c724HSYw6X0K63o+ecpeTn4t92Q=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=twohJJ8smdG94+ivCw6JHpWyxc/qnlszhBccWg+IT0PNCF6RLAbwgvtAb4DN2qECG 1blRjx5cbIoNeAlvlElPmqUE78cShdo48RyrAA0wLts+zAOpVLveOXrx4KpCvFVSMQ 02DnOiltWrfxfI2rKpgeeftVW5Yy+cB37A0sQmus= Date: Thu, 22 Jul 2021 15:16:17 +0200 From: Greg KH To: "Wang, Zhi A" Cc: Christoph Hellwig , Jani Nikula , Joonas Lahtinen , "Vivi, Rodrigo" , Zhenyu Wang , "intel-gfx@lists.freedesktop.org" , "intel-gvt-dev@lists.freedesktop.org" , "dri-devel@lists.freedesktop.org" , "linux-kernel@vger.kernel.org" Subject: Re: refactor the i915 GVT support Message-ID: References: <20210721155355.173183-1-hch@lst.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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