Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp2903352ybl; Fri, 20 Dec 2019 00:08:18 -0800 (PST) X-Google-Smtp-Source: APXvYqz9CAMSmAfbDYxAFYh4NIB7YIbqkbScJLf5JojYknXmbqs2BfKfpZSZbiaXr2DHK8vb6bq1 X-Received: by 2002:a9d:5c88:: with SMTP id a8mr12861140oti.348.1576829298447; Fri, 20 Dec 2019 00:08:18 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1576829298; cv=none; d=google.com; s=arc-20160816; b=vJYiW9B/3UrJF18HmAMV/QHqyfXsHaKO414Tz7s0/G5KpznD8U6ih9UHP9BLrr/AKh cfH7xLOPCctGPktTNhuEDB4oUGdtf81jI3c4gX2P3iMBLTUSZUXBgJJis09yHMI8Drhf bAGnJlpx1B6Y0C9xXRq9JBQu+fnXdLnqXHGioC8w9hwTk3uZONON+ba8SWdXhc2AKjZ5 wHalq6A1E6uuFOhJlkpzr3eJx4qsLc3vEoM6h8yJAQ2T4KS7nvM+I9fV6ountzBRiWRk 7R4PmuLegzVuYhJRbG/anB4Zk7W0UIpZahYjnEh3PVTXKJ5Et9L99CblAky8ikLg83VV 1Vlg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-language :content-transfer-encoding:in-reply-to:mime-version:user-agent:date :message-id:organization:references:cc:to:from:subject :dkim-signature; bh=KMpxBZGtalz7Tw4qD60l9z3E93X78iUlXteqDfL3jyw=; b=A/YNekD9/rtIFjMeoQOJrt2p5mn0PQX4kPFlJ8ySi98zmz80rUrYuEWMBVZOTn3lCt uRM1WkvWZXM+b1JoiLzQhA+AVrVlRn/CvnEjLKoohgGNrlv1LPVrRz90FpKMh3T3z3qU ZYx1jODODhaIMDD+gAQbN7B1iScfbVxV0g3IQ6OLzx6UttVGaOzAE65EIGCAnDWzH3Lv E/W31+n16jIwPR/fkAtxpIZaiei5PZW8Vg6HgkSFG4RoDk8Cg8efov4/qNyefSqAySFi T46l7kOB7KzSo7oqqWpz4S2x+1AjQj4ZZD3qeYX6tRLN7qY4Gpdwj92Oeo9ne1JocI57 5RYw== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail (test mode) header.i=@shipmail.org header.s=mail header.b=p3sd2f8Z; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id v25si2878479ote.261.2019.12.20.00.08.06; Fri, 20 Dec 2019 00:08:18 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=fail (test mode) header.i=@shipmail.org header.s=mail header.b=p3sd2f8Z; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727193AbfLTIGT (ORCPT + 99 others); Fri, 20 Dec 2019 03:06:19 -0500 Received: from pio-pvt-msa2.bahnhof.se ([79.136.2.41]:44264 "EHLO pio-pvt-msa2.bahnhof.se" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725965AbfLTIGT (ORCPT ); Fri, 20 Dec 2019 03:06:19 -0500 Received: from localhost (localhost [127.0.0.1]) by pio-pvt-msa2.bahnhof.se (Postfix) with ESMTP id E18D23F39C; Fri, 20 Dec 2019 09:06:16 +0100 (CET) Authentication-Results: pio-pvt-msa2.bahnhof.se; dkim=pass (1024-bit key; unprotected) header.d=shipmail.org header.i=@shipmail.org header.b=p3sd2f8Z; dkim-atps=neutral X-Virus-Scanned: Debian amavisd-new at bahnhof.se X-Spam-Flag: NO X-Spam-Score: -2.099 X-Spam-Level: X-Spam-Status: No, score=-2.099 tagged_above=-999 required=6.31 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Received: from pio-pvt-msa2.bahnhof.se ([127.0.0.1]) by localhost (pio-pvt-msa2.bahnhof.se [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X975R5nw9Zgj; Fri, 20 Dec 2019 09:06:15 +0100 (CET) Received: from mail1.shipmail.org (h-205-35.A357.priv.bahnhof.se [155.4.205.35]) (Authenticated sender: mb878879) by pio-pvt-msa2.bahnhof.se (Postfix) with ESMTPA id E5BAC3F5AD; Fri, 20 Dec 2019 09:06:09 +0100 (CET) Received: from localhost.localdomain (h-205-35.A357.priv.bahnhof.se [155.4.205.35]) by mail1.shipmail.org (Postfix) with ESMTPSA id E6E6B36215B; Fri, 20 Dec 2019 09:06:08 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=shipmail.org; s=mail; t=1576829169; bh=Q2+zsn1qCmWl8yYgXnf252a2g92KszZb+cwwyH5RgCo=; h=Subject:From:To:Cc:References:Date:In-Reply-To:From; b=p3sd2f8ZZmX+4iXnUTLPMIFKc6tKabjE4bXiMCS3K45uQ3jcgbSyOI8kT3MYfBZA2 oBJDjhM2bPK/1aJ+6OKK0E17wXlaSX84YE7OmGpNfyt8MVMeDfaah0vTz9W5XAW+I9 nTsjpKTa4R5PZhmxaiwEK0cbgeBb51SqgAF8Zt6o= Subject: Ack to merge through DRM tree? WAS [PATCH v4 0/2] mm, drm/ttm: Fix pte insertion with customized protection From: =?UTF-8?Q?Thomas_Hellstr=c3=b6m_=28VMware=29?= To: linux-mm@kvack.org, linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org, Andrew Morton , Michal Hocko Cc: pv-drivers@vmware.com, linux-graphics-maintainer@vmware.com, Thomas Hellstrom , "Matthew Wilcox (Oracle)" , "Kirill A. Shutemov" , Ralph Campbell , =?UTF-8?B?SsOpcsO0bWUgR2xpc3Nl?= , =?UTF-8?Q?Christian_K=c3=b6nig?= References: <20191212084741.9251-1-thomas_os@shipmail.org> Organization: VMware Inc. Message-ID: Date: Fri, 20 Dec 2019 09:06:08 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: <20191212084741.9251-1-thomas_os@shipmail.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Andrew, On 12/12/19 9:47 AM, Thomas Hellström (VMware) wrote: > From: Thomas Hellstrom > > The drm/ttm module is using a modified on-stack copy of the > struct vm_area_struct to be able to set a page protection with customized > caching. Fix that by adding a vmf_insert_mixed_prot() function similar > to the existing vmf_insert_pfn_prot() for use with drm/ttm. > > I'd like to merge this through a drm tree. > > Changes since v1: > *) Formatting fixes in patch 1 > *) Updated commit message of patch 2. > Changes since v2: > *) Moved vmf_insert_mixed_prot() export to patch 2 (Michal Hocko) > *) Documented under which conditions it's safe to use a page protection > different from struct vm_area_struct::vm_page_prot. (Michal Hocko) > Changes since v3: > *) More documentation regarding under which conditions it's safe to use a > page protection different from struct vm_area_struct::vm_page_prot. This > time also in core vm. (Michal Hocko) > > Cc: Andrew Morton > Cc: Michal Hocko > Cc: "Matthew Wilcox (Oracle)" > Cc: "Kirill A. Shutemov" > Cc: Ralph Campbell > Cc: "Jérôme Glisse" > Cc: "Christian König" > Seems all concerns with this series have been addressed. Could I have an ack to merge this through a DRM tree? Thanks, Thomas