Received: by 2002:a05:6a10:22f:0:0:0:0 with SMTP id 15csp2901914pxk; Mon, 28 Sep 2020 03:17:54 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzxk0mBMBWsy2HqhyzkMg5Jl9ievv7+E2N/Y234mrbXcdT/Qsapp91w/CqfTmsITqzp25vH X-Received: by 2002:a50:e799:: with SMTP id b25mr826485edn.225.1601288273831; Mon, 28 Sep 2020 03:17:53 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1601288273; cv=none; d=google.com; s=arc-20160816; b=IrYoHEU3mbANID808fLa2C8Oui+A4qZ2k8rtN6CiZaKYGsMrzAPoCH6E9vz2WtZmG9 p8oIqJqTipy/fKWY25WzJNEcd1yvJvvfZ4P/0QtRBIG0yg5FsTBaxRP5Ome7N5CJ9A9w Z2qAMcDyPVaPEQ7RV+vasLdgO54ea9Em6EdoTxu8P9drz5lsvlxijRHVC6PsfrRor/r1 N1eWSr8UDIZwMt6rSbPidt1St8zNexv0XmekZbyPzxGRF7F+3NJqsaeT1o3CtJ8wsMim X+qNFQzXdLPUnUPU05SQlbhUSKsOHrezDJY3PF+4569C+BzOUTbvkENxIG8cI4X5H+XH QbMg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:date:user-agent:message-id:organization:cc:from :to:subject:references:in-reply-to:content-transfer-encoding :mime-version:ironport-sdr:ironport-sdr; bh=QR8+rZ9Kjyf0oTwnZQ6obwFYPKopkbeKBTRWAx+60Xo=; b=D6aGSY0h27iV8fIg9IZgmyezSPsJgp7jFrdDK6GNcqG9fUHAdyvt4kVn+ND8g9zAre aONkVjuwDdqSk4vTrYUJ68sv2lp/0OyyJZowqWDyBp2j1eOjCkq6SbkIS7Mqlk4JCqzY Zvr/GGJ0AgAb4si9wvU2+q8AwIFTIn1mzoSKA2BWW6njVeiz3QZIgblIxcALaAQvijBF rC90RnxbPcW70vlvU+dgGZgIcfp3SypR8XYCcscP0U/URPvjtqOWKd/+Ap8JzYt833vh qBxEVR4imyDVZ+TUAOc0U2VeO2fQAW3OV02MH/kf0Heqi6yMPCgZ5CXZRt6SpqLcJPQc r3jA== ARC-Authentication-Results: i=1; mx.google.com; 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=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id b43si293935edf.503.2020.09.28.03.17.30; Mon, 28 Sep 2020 03:17:53 -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; 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=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726694AbgI1KNt convert rfc822-to-8bit (ORCPT + 99 others); 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