From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.8 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 4D6F8C2D0A8 for ; Mon, 28 Sep 2020 10:13:50 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 1BD8D23119 for ; Mon, 28 Sep 2020 10:13:50 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726709AbgI1KNt convert rfc822-to-8bit (ORCPT ); Mon, 28 Sep 2020 06:13:49 -0400 Received: from mga01.intel.com ([192.55.52.88]:28447 "EHLO mga01.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726564AbgI1KNs (ORCPT ); Mon, 28 Sep 2020 06:13:48 -0400 IronPort-SDR: vJxDrUcG9dz3BuJFcj+XCdvjunMZqD0Kcde9x3VEfzkcViNDFxqRAyILjETuJAKFkr0Ut+acA5 r4f7UdNiab2Q== X-IronPort-AV: E=McAfee;i="6000,8403,9757"; a="180124701" X-IronPort-AV: E=Sophos;i="5.77,313,1596524400"; d="scan'208";a="180124701" X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga004.jf.intel.com ([10.7.209.38]) by fmsmga101.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 28 Sep 2020 03:13:47 -0700 IronPort-SDR: oynyLpLaEo8E2hmYKjUK2eLejsF9h1nd7bvB1+8YkaeLPVcxKUTeXs7JzHnC+u3AXBq2RQNnIu AssYzP9UKYBw== X-IronPort-AV: E=Sophos;i="5.77,313,1596524400"; d="scan'208";a="456766108" Received: from jrcarrol-mobl.ger.corp.intel.com (HELO localhost) ([10.252.31.240]) by orsmga004-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 28 Sep 2020 03:13:41 -0700 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8BIT In-Reply-To: <20200926062959.GA3427@lst.de> References: <20200924135853.875294-1-hch@lst.de> <20200925194349.d0ee9dbedb2ec48f0bfcd2ec@linux-foundation.org> <20200926062959.GA3427@lst.de> Subject: Re: remove alloc_vm_area v2 To: Andrew Morton , Christoph Hellwig , David Airlie , Daniel Vetter , Stephen Rothwell From: Joonas Lahtinen Cc: Christoph Hellwig , Peter Zijlstra , Boris Ostrovsky , Juergen Gross , Stefano Stabellini , Jani Nikula , Tvrtko Ursulin , Chris Wilson , Matthew Auld , Rodrigo Vivi , Minchan Kim , Matthew Wilcox , Nitin Gupta , x86@kernel.org, xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org, intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org, linux-mm@kvack.org Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo Message-ID: <160128801808.6464.1013594053120198786@jlahtine-mobl.ger.corp.intel.com> User-Agent: alot/0.8.1 Date: Mon, 28 Sep 2020 13:13:38 +0300 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org + Dave and Daniel + Stephen Quoting Christoph Hellwig (2020-09-26 09:29:59) > On Fri, Sep 25, 2020 at 07:43:49PM -0700, Andrew Morton wrote: > > On Thu, 24 Sep 2020 15:58:42 +0200 Christoph Hellwig wrote: > > > > > this series removes alloc_vm_area, which was left over from the big > > > vmalloc interface rework. It is a rather arkane interface, basicaly > > > the equivalent of get_vm_area + actually faulting in all PTEs in > > > the allocated area. It was originally addeds for Xen (which isn't > > > modular to start with), and then grew users in zsmalloc and i915 > > > which seems to mostly qualify as abuses of the interface, especially > > > for i915 as a random driver should not set up PTE bits directly. > > > > > > Note that the i915 patches apply to the drm-tip branch of the drm-tip > > > tree, as that tree has recent conflicting commits in the same area. > > > > Is the drm-tip material in linux-next yet? I'm still seeing a non-trivial > > reject in there at present. > > I assumed it was, but the reject imply that they aren't. Tvrtko, do you > know the details? I think we have a gap that after splitting the drm-intel-next pull requests into two the drm-intel/for-linux-next branch is now missing material from drm-intel/drm-intel-gt-next. I think a simple course of action might be to start including drm-intel-gt-next in linux-next, which would mean that we should update DIM tooling to add extra branch "drm-intel/gt-for-linux-next" or so. Which specific patches are missing in this case? Regards, Joonas From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.8 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 43B76C47420 for ; Mon, 28 Sep 2020 10:13:54 +0000 (UTC) Received: from gabe.freedesktop.org (gabe.freedesktop.org [131.252.210.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id F39DA20809 for ; Mon, 28 Sep 2020 10:13:53 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org F39DA20809 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=linux.intel.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=dri-devel-bounces@lists.freedesktop.org Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id 813E76E113; Mon, 28 Sep 2020 10:13:51 +0000 (UTC) Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by gabe.freedesktop.org (Postfix) with ESMTPS id 321AA89F8E; Mon, 28 Sep 2020 10:13:50 +0000 (UTC) IronPort-SDR: ifmlwUl4aDrxFAMWZhMU2qhwXOe5rLot1YtYxn1NugFnSD4xvu3EWL6FodP41Pqjo55wHy13pr VUvZTjiwUVWw== X-IronPort-AV: E=McAfee;i="6000,8403,9757"; a="159312100" X-IronPort-AV: E=Sophos;i="5.77,313,1596524400"; d="scan'208";a="159312100" X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga004.jf.intel.com ([10.7.209.38]) by fmsmga102.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 28 Sep 2020 03:13:47 -0700 IronPort-SDR: oynyLpLaEo8E2hmYKjUK2eLejsF9h1nd7bvB1+8YkaeLPVcxKUTeXs7JzHnC+u3AXBq2RQNnIu AssYzP9UKYBw== X-IronPort-AV: E=Sophos;i="5.77,313,1596524400"; d="scan'208";a="456766108" Received: from jrcarrol-mobl.ger.corp.intel.com (HELO localhost) ([10.252.31.240]) by orsmga004-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 28 Sep 2020 03:13:41 -0700 MIME-Version: 1.0 In-Reply-To: <20200926062959.GA3427@lst.de> References: <20200924135853.875294-1-hch@lst.de> <20200925194349.d0ee9dbedb2ec48f0bfcd2ec@linux-foundation.org> <20200926062959.GA3427@lst.de> Subject: Re: remove alloc_vm_area v2 To: Andrew Morton , Christoph Hellwig , David Airlie , Daniel Vetter , Stephen Rothwell From: Joonas Lahtinen Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo Message-ID: <160128801808.6464.1013594053120198786@jlahtine-mobl.ger.corp.intel.com> User-Agent: alot/0.8.1 Date: Mon, 28 Sep 2020 13:13:38 +0300 X-BeenThere: dri-devel@lists.freedesktop.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Direct Rendering Infrastructure - Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Juergen Gross , Tvrtko Ursulin , Stefano Stabellini , Matthew Wilcox , dri-devel@lists.freedesktop.org, linux-mm@kvack.org, Peter Zijlstra , intel-gfx@lists.freedesktop.org, x86@kernel.org, linux-kernel@vger.kernel.org, Chris Wilson , Minchan Kim , Matthew Auld , Rodrigo Vivi , xen-devel@lists.xenproject.org, Boris Ostrovsky , Christoph Hellwig , Nitin Gupta Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" + Dave and Daniel + Stephen Quoting Christoph Hellwig (2020-09-26 09:29:59) > On Fri, Sep 25, 2020 at 07:43:49PM -0700, Andrew Morton wrote: > > On Thu, 24 Sep 2020 15:58:42 +0200 Christoph Hellwig wrote: > > > > > this series removes alloc_vm_area, which was left over from the big > > > vmalloc interface rework. It is a rather arkane interface, basicaly > > > the equivalent of get_vm_area + actually faulting in all PTEs in > > > the allocated area. It was originally addeds for Xen (which isn't > > > modular to start with), and then grew users in zsmalloc and i915 > > > which seems to mostly qualify as abuses of the interface, especially > > > for i915 as a random driver should not set up PTE bits directly. > > > > > > Note that the i915 patches apply to the drm-tip branch of the drm-tip > > > tree, as that tree has recent conflicting commits in the same area. > > > > Is the drm-tip material in linux-next yet? I'm still seeing a non-trivial > > reject in there at present. > > I assumed it was, but the reject imply that they aren't. Tvrtko, do you > know the details? I think we have a gap that after splitting the drm-intel-next pull requests into two the drm-intel/for-linux-next branch is now missing material from drm-intel/drm-intel-gt-next. I think a simple course of action might be to start including drm-intel-gt-next in linux-next, which would mean that we should update DIM tooling to add extra branch "drm-intel/gt-for-linux-next" or so. Which specific patches are missing in this case? Regards, Joonas _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.8 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 13234C4727F for ; Mon, 28 Sep 2020 10:13:52 +0000 (UTC) Received: from gabe.freedesktop.org (gabe.freedesktop.org [131.252.210.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id B814220756 for ; Mon, 28 Sep 2020 10:13:51 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org B814220756 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=linux.intel.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=intel-gfx-bounces@lists.freedesktop.org Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id 02B5089F8E; Mon, 28 Sep 2020 10:13:51 +0000 (UTC) Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by gabe.freedesktop.org (Postfix) with ESMTPS id 321AA89F8E; Mon, 28 Sep 2020 10:13:50 +0000 (UTC) IronPort-SDR: ifmlwUl4aDrxFAMWZhMU2qhwXOe5rLot1YtYxn1NugFnSD4xvu3EWL6FodP41Pqjo55wHy13pr VUvZTjiwUVWw== X-IronPort-AV: E=McAfee;i="6000,8403,9757"; a="159312100" X-IronPort-AV: E=Sophos;i="5.77,313,1596524400"; d="scan'208";a="159312100" X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga004.jf.intel.com ([10.7.209.38]) by fmsmga102.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 28 Sep 2020 03:13:47 -0700 IronPort-SDR: oynyLpLaEo8E2hmYKjUK2eLejsF9h1nd7bvB1+8YkaeLPVcxKUTeXs7JzHnC+u3AXBq2RQNnIu AssYzP9UKYBw== X-IronPort-AV: E=Sophos;i="5.77,313,1596524400"; d="scan'208";a="456766108" Received: from jrcarrol-mobl.ger.corp.intel.com (HELO localhost) ([10.252.31.240]) by orsmga004-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 28 Sep 2020 03:13:41 -0700 MIME-Version: 1.0 In-Reply-To: <20200926062959.GA3427@lst.de> References: <20200924135853.875294-1-hch@lst.de> <20200925194349.d0ee9dbedb2ec48f0bfcd2ec@linux-foundation.org> <20200926062959.GA3427@lst.de> To: Andrew Morton , Christoph Hellwig , David Airlie , Daniel Vetter , Stephen Rothwell From: Joonas Lahtinen Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo Message-ID: <160128801808.6464.1013594053120198786@jlahtine-mobl.ger.corp.intel.com> User-Agent: alot/0.8.1 Date: Mon, 28 Sep 2020 13:13:38 +0300 Subject: Re: [Intel-gfx] remove alloc_vm_area v2 X-BeenThere: intel-gfx@lists.freedesktop.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Intel graphics driver community testing & development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Juergen Gross , Stefano Stabellini , Matthew Wilcox , dri-devel@lists.freedesktop.org, linux-mm@kvack.org, Peter Zijlstra , intel-gfx@lists.freedesktop.org, x86@kernel.org, linux-kernel@vger.kernel.org, Chris Wilson , Minchan Kim , Matthew Auld , xen-devel@lists.xenproject.org, Boris Ostrovsky , Christoph Hellwig , Nitin Gupta Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: intel-gfx-bounces@lists.freedesktop.org Sender: "Intel-gfx" + Dave and Daniel + Stephen Quoting Christoph Hellwig (2020-09-26 09:29:59) > On Fri, Sep 25, 2020 at 07:43:49PM -0700, Andrew Morton wrote: > > On Thu, 24 Sep 2020 15:58:42 +0200 Christoph Hellwig wrote: > > > > > this series removes alloc_vm_area, which was left over from the big > > > vmalloc interface rework. It is a rather arkane interface, basicaly > > > the equivalent of get_vm_area + actually faulting in all PTEs in > > > the allocated area. It was originally addeds for Xen (which isn't > > > modular to start with), and then grew users in zsmalloc and i915 > > > which seems to mostly qualify as abuses of the interface, especially > > > for i915 as a random driver should not set up PTE bits directly. > > > > > > Note that the i915 patches apply to the drm-tip branch of the drm-tip > > > tree, as that tree has recent conflicting commits in the same area. > > > > Is the drm-tip material in linux-next yet? I'm still seeing a non-trivial > > reject in there at present. > > I assumed it was, but the reject imply that they aren't. Tvrtko, do you > know the details? I think we have a gap that after splitting the drm-intel-next pull requests into two the drm-intel/for-linux-next branch is now missing material from drm-intel/drm-intel-gt-next. I think a simple course of action might be to start including drm-intel-gt-next in linux-next, which would mean that we should update DIM tooling to add extra branch "drm-intel/gt-for-linux-next" or so. Which specific patches are missing in this case? Regards, Joonas _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx