Received: by 10.192.165.156 with SMTP id m28csp203221imm; Tue, 17 Apr 2018 08:46:37 -0700 (PDT) X-Google-Smtp-Source: AIpwx4+RK6ua+b2oogNphq03bA+0GS/3Xl3Ah3A0vzFYahifKWohOcp7Ph8zkMGuzneqc/med36E X-Received: by 10.99.148.1 with SMTP id m1mr2222590pge.140.1523979997403; Tue, 17 Apr 2018 08:46:37 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1523979997; cv=none; d=google.com; s=arc-20160816; b=VM95btw/iSttOzXv5newHuN/g4JRtV8rHnjJDSJPXApGXnG9TUE55ScJQmAn2U2NQa 2DZkT/Jtbl+aV063L+1icrXZOMoe/igzHp2EImrTzbSpuEAXNso5nzRuCBsejx2sx9NY vzXKersnXL+tdtuQKPPj2SUfYWW4ffsv3UGfb0KgzQHBdrztJWp4LyUjPob44uWG8CIk N1dgt9NFBa25BTLF7sAocSRWb2Hu0vkGUDqZdJmgvgYeWR/EqvMhbgd42GHmgVbchfdI tCidOlC92sbEUnXrfK6dBNtY5MBM+aK2VlnWPnNgmfqbcEi7FPgLEWz/e/PbCoHBJaaL sGaw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :references:in-reply-to:mime-version:dkim-signature :arc-authentication-results; bh=Zo9lIkj+3fs5rbpJyO92ryo/LSck92hZ335pTI/63I4=; b=P69QRMjmdHRhUBQUXlpRdH+XjBCsWmfYuVqN6N93Rn8Q+J0ilgyZFHiK7zA+0LcVOt Nify2vQeJoiDA/uZt5ccTfBVk8zOYcoSmDHxuXwZSNCIsHdWz4juMuRVOXJ/Sh8hxrd5 ETYQLNERz38NLMb6Q5lyS938PwJWTN48Sp1FJfw3c7+4jSS/LL8a+c/9GjESDswkJ6W4 jet7XBjvxjQ9OZBr7I5Ix+r997xuaSGOufw/r4kyCNsKWvvNdp5Pu8APS4gECJZtIduD wRROJCfCBX8HkwFjxHVilCk9/ecP9MOYbkwhJkF0asUdFvm57myi+eDphyKBQR1NAd+d GpZw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=BaPEAXWS; 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; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id bd8-v6si10240132plb.96.2018.04.17.08.46.23; Tue, 17 Apr 2018 08:46:37 -0700 (PDT) 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=pass header.i=@gmail.com header.s=20161025 header.b=BaPEAXWS; 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; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752887AbeDQPog (ORCPT + 99 others); Tue, 17 Apr 2018 11:44:36 -0400 Received: from mail-lf0-f68.google.com ([209.85.215.68]:43876 "EHLO mail-lf0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750741AbeDQPof (ORCPT ); Tue, 17 Apr 2018 11:44:35 -0400 Received: by mail-lf0-f68.google.com with SMTP id v207-v6so28017032lfa.10 for ; Tue, 17 Apr 2018 08:44:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=Zo9lIkj+3fs5rbpJyO92ryo/LSck92hZ335pTI/63I4=; b=BaPEAXWSB5u4Y7Vb+ZiSOQZjlPlqWERTVf49+FANt7toMlSKGwIWYSTJvlYYIFBA0c GLJZhD+j7utJs1lfV6690NqTBsqLiryjXOQ1Hv4oBKT7WBAB/hCuvOT3IZqvuJ6LpBAz aI6sbpS7ORnj5j3MzbDJXk6W+ua3+yxujHKwmXnrXRfxm87oz/92TQgSesQ0YEEAtmBZ SZ28F92Kb0EJ1Es6C8cc3yujDQBcntu2IyL/ytkYnyTPcKswuuHkvo/bt2U8wNEWQCwl Qz9m4CKxE7lLpkx6e1OAI3jweOh5meDwi7JApl/QKVgTV40yU1Qlj/ZTPbxrCSxV70GI jQqw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=Zo9lIkj+3fs5rbpJyO92ryo/LSck92hZ335pTI/63I4=; b=qxL1gg3ZlWcJ4V7szK/AmVYBcsGf0gZK5w61TwHI4yB14MGvRECrLwiaN/LOlvnaP8 IzAa4CxqlNF7XjyhHYroLd4uCMPhx0iWHxWNxBQoX7UOuKVUBAtoKCGT8ZazPRf2fh5x riS4WMzQ2ySeRvhYc+bVqGP8dlbLh9tSGPreiNpnCCbeuZFYje7R6pkdjmDLEieAdoFe nFT69YPD2SWziRkFwtGX7Kf66RoR4qg+oErij25H2AgHsHv8o44EwH3eTizgPRFRRh/G xrop8+mHAILJJmm7XjgcPiPTjYMDD1ks1s3n01cXby+TDF3ytZ3o5ZJGmz5+VKVLlb52 stYQ== X-Gm-Message-State: ALQs6tBtKBMzXPyXUuFzh1enSbR9X6EzQlgs4VtEpjTUWk98mCQUqbIS xXXEft2uNzU3yao3COS7IUqAw/1t8YyJ44h49dE= X-Received: by 10.46.159.70 with SMTP id v6mr1855896ljk.31.1523979873539; Tue, 17 Apr 2018 08:44:33 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a19:150e:0:0:0:0:0 with HTTP; Tue, 17 Apr 2018 08:44:32 -0700 (PDT) In-Reply-To: <87h8o9g8be.fsf@intel.com> References: <20180417151127.GA31655@jordon-HP-15-Notebook-PC> <87h8o9g8be.fsf@intel.com> From: Souptick Joarder Date: Tue, 17 Apr 2018 21:14:32 +0530 Message-ID: Subject: Re: [PATCH] gpu: drm: i915: Change return type to vm_fault_t To: Jani Nikula Cc: joonas.lahtinen@linux.intel.com, rodrigo.vivi@intel.com, airlied@linux.ie, intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org, Matthew Wilcox Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Not exactly. The plan for these patches is to introduce new vm_fault_t type in vm_operations_struct fault handlers. It's now available in 4.17-rc1. We will push all the required drivers/filesystem changes through different maintainers to linus tree. Once everything is converted into vm_fault_t type then Changing it from a signed to an unsigned int causes GCC to warn about an assignment from an incompatible type -- int foo(void) is incompatible with unsigned int foo(void). Please refer 1c8f422059ae ("mm: change return type to vm_fault_t") in 4.17-rc1. On Tue, Apr 17, 2018 at 8:59 PM, Jani Nikula wrote: > On Tue, 17 Apr 2018, Souptick Joarder wrote: >> Use new return type vm_fault_t for fault handler. For >> now, this is just documenting that the function returns >> a VM_FAULT value rather than an errno. Once all instances >> are converted, vm_fault_t will become a distinct type. >> >> Reference id -> 1c8f422059ae ("mm: change return type to >> vm_fault_t") >> >> Signed-off-by: Souptick Joarder >> --- >> drivers/gpu/drm/i915/i915_drv.h | 3 ++- >> drivers/gpu/drm/i915/i915_gem.c | 15 ++++++++------- >> 2 files changed, 10 insertions(+), 8 deletions(-) >> >> diff --git a/drivers/gpu/drm/i915/i915_drv.h b/drivers/gpu/drm/i915/i915_drv.h >> index a42deeb..95b0d50 100644 >> --- a/drivers/gpu/drm/i915/i915_drv.h >> +++ b/drivers/gpu/drm/i915/i915_drv.h >> @@ -51,6 +51,7 @@ >> #include >> #include >> #include >> +#include >> >> #include "i915_params.h" >> #include "i915_reg.h" >> @@ -3363,7 +3364,7 @@ int i915_gem_wait_for_idle(struct drm_i915_private *dev_priv, >> unsigned int flags); >> int __must_check i915_gem_suspend(struct drm_i915_private *dev_priv); >> void i915_gem_resume(struct drm_i915_private *dev_priv); >> -int i915_gem_fault(struct vm_fault *vmf); >> +vm_fault_t i915_gem_fault(struct vm_fault *vmf); >> int i915_gem_object_wait(struct drm_i915_gem_object *obj, >> unsigned int flags, >> long timeout, >> diff --git a/drivers/gpu/drm/i915/i915_gem.c b/drivers/gpu/drm/i915/i915_gem.c >> index dd89abd..bdac690 100644 >> --- a/drivers/gpu/drm/i915/i915_gem.c >> +++ b/drivers/gpu/drm/i915/i915_gem.c >> @@ -1882,7 +1882,7 @@ int i915_gem_mmap_gtt_version(void) >> * The current feature set supported by i915_gem_fault() and thus GTT mmaps >> * is exposed via I915_PARAM_MMAP_GTT_VERSION (see i915_gem_mmap_gtt_version). >> */ >> -int i915_gem_fault(struct vm_fault *vmf) >> +vm_fault_t i915_gem_fault(struct vm_fault *vmf) >> { >> #define MIN_CHUNK_PAGES ((1 << 20) >> PAGE_SHIFT) /* 1 MiB */ >> struct vm_area_struct *area = vmf->vma; >> @@ -1895,6 +1895,7 @@ int i915_gem_fault(struct vm_fault *vmf) >> pgoff_t page_offset; >> unsigned int flags; >> int ret; >> + vm_fault_t retval; > > What's the point of changing the name? An unnecessary change. > > BR, > Jani. > >> >> /* We don't use vmf->pgoff since that has the fake offset */ >> page_offset = (vmf->address - area->vm_start) >> PAGE_SHIFT; >> @@ -2000,7 +2001,7 @@ int i915_gem_fault(struct vm_fault *vmf) >> * and so needs to be reported. >> */ >> if (!i915_terminally_wedged(&dev_priv->gpu_error)) { >> - ret = VM_FAULT_SIGBUS; >> + retval = VM_FAULT_SIGBUS; >> break; >> } >> case -EAGAIN: >> @@ -2017,21 +2018,21 @@ int i915_gem_fault(struct vm_fault *vmf) >> * EBUSY is ok: this just means that another thread >> * already did the job. >> */ >> - ret = VM_FAULT_NOPAGE; >> + retval = VM_FAULT_NOPAGE; >> break; >> case -ENOMEM: >> - ret = VM_FAULT_OOM; >> + retval = VM_FAULT_OOM; >> break; >> case -ENOSPC: >> case -EFAULT: >> - ret = VM_FAULT_SIGBUS; >> + retval = VM_FAULT_SIGBUS; >> break; >> default: >> WARN_ONCE(ret, "unhandled error in i915_gem_fault: %i\n", ret); >> - ret = VM_FAULT_SIGBUS; >> + retval = VM_FAULT_SIGBUS; >> break; >> } >> - return ret; >> + return retval; >> } >> >> static void __i915_gem_object_release_mmap(struct drm_i915_gem_object *obj) >> -- >> 1.9.1 >> > > -- > Jani Nikula, Intel Open Source Technology Center