Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp313836yba; Fri, 26 Apr 2019 00:01:36 -0700 (PDT) X-Google-Smtp-Source: APXvYqy1iy9iuUItp+nRVOS8pGh4WfF2c6vbquNU94Z2/ZYU1LROaJ4dQ/98fzeUEQ5sasuLOpzh X-Received: by 2002:a65:5009:: with SMTP id f9mr41621971pgo.390.1556262095888; Fri, 26 Apr 2019 00:01:35 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1556262095; cv=none; d=google.com; s=arc-20160816; b=ghdM9BPyIlTjbvVJ4ldsI5nfyUMsBy+oF8IsCT4PygfEqJ8vrN8dxWT63ASP+8YFiK f4W+UXCF9sLXJO0kec8+37gqGGFi3uq0JNOdVp8FwPF3PGLCTfvZsY+v/1aFJy752X5J 35iUIjQWAR6GjuhCgZTRdX5ayUEqrmgWEr1DxuXzNh3G+FVM2hQ2SQdqd6Hz5qv82hFY +JA0LUZSDD0EqjOkheQEd54RT9QDoHYG74E3oQoJbx9eA1+u6V/ClbkOH3XfsjLlNprc DMDHTJw/w6tmNNAfSXyGmBjG+Ffd6PVO1AG8ppdiTZPIWYC1ECqtNbMZcIpdtiiJXICs kTEw== 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 :in-reply-to:references:mime-version:dkim-signature; bh=ZWWiy6HsjxsTUoo2P8LqlCvN+4wOu2xo/zLBn5M2klI=; b=0qqNahoELNNrYnjkvCcYvjqaQ8T5FM7a/+s6iiSJ69Kljvbm9H78k47um4yvdf7cB4 HcMJTKvqi0AKN3TPV+mZCmBETwHI2YfyErFgvJpXPIzPC9fYaYVN9n6rPXGEFEUGA0M3 tLi7eB38XmEa/ckiCTFU0bwzLL4rKndBLQxDcM+dtw3AOjkur41erME/vxE1o3iPeFRF Q2yOBbgRteDZCtahPgCCd9x33yD/Wd8uTj3KSBsF4w3qMywkiuNpU7Oi5lQZ7f8ajHqu /r+qp4A7FQx3XAvQt7huQ04BwRVkmZ/51nDQ5hOXUIOh4xiHZbB0ZKVAge9wFXwMfvHL cgAQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=feBq2Lk1; 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 q4si22679710pgv.474.2019.04.26.00.01.20; Fri, 26 Apr 2019 00:01:35 -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=feBq2Lk1; 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 S1725993AbfDZHAG (ORCPT + 99 others); Fri, 26 Apr 2019 03:00:06 -0400 Received: from mail-qt1-f196.google.com ([209.85.160.196]:45535 "EHLO mail-qt1-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725899AbfDZHAF (ORCPT ); Fri, 26 Apr 2019 03:00:05 -0400 Received: by mail-qt1-f196.google.com with SMTP id b3so2943122qtc.12 for ; Fri, 26 Apr 2019 00:00:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ZWWiy6HsjxsTUoo2P8LqlCvN+4wOu2xo/zLBn5M2klI=; b=feBq2Lk1ARm/qsqxxZhRnmuYFTRmBz8mnxKRa9gj+R07PekBu6B6KgQwAJXs6yfu1w DYxVTTfyO4IWCWGhU9dbTC7+NJDKyxXy1kiZg2djscgSmr3VLwVIPEilGT1GUES9/aQ9 m7UKTHutH5aQ0qBZAcJm3XraogE6UF7UF7GlLK+yzVodJ64hdeifCSsizMvi0Qjd2cUa 95ZcNzXGDDXxmA+9+cnMTD/gZxJnNARAepc/M6CyPNTMOB/8NT0lBosmwRIqWFqgwx+Z 954tN5H5dPMTCAiUmmsM8+1GrdCz1OMeRnJJy74NUOdmgOG/39+hBhiQbvDnVe08OA1A Gy2Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ZWWiy6HsjxsTUoo2P8LqlCvN+4wOu2xo/zLBn5M2klI=; b=AyKJtaCN1YFOO+pzpH4wQDWVkGsj4GizDg0kj9bzSPkcrVUsm3KC/LmEHSuUMKg5ij N0z910H8awREbiFYKDnNjk+Hy8SCLA4sTKHevAQzIFXNzMdAlgWA0ITOoosJkaKw+kk8 ss80VTKEKOoMEMGku7Hkm9WouTTeYmoXFn0GzUJBGGYncqC0Ae+0X31g/HpefuF+Mcdz ce/oDCo6yFr+WtrsEcTyzLUxc56o2N013aehwfDclw3gwnezVEPt84j1zMOdBkG1L+hC tKORr2/8jTx7uqT/nBV8ms5M6iSP0JHAW+pjGC9adDBuTJ7PY6lKnzLqRiGjuAqjiJVO ec/g== X-Gm-Message-State: APjAAAWQdoFuEFFMvtCIXXIWYdDDr3xOTlnChUmL96vLL6IVRaUsQwPi Mlv4EWxVIOzRFxo/ShYQ6gXIwUsJ4zkcAu2Er2k= X-Received: by 2002:ac8:26e1:: with SMTP id 30mr454596qtp.305.1556262005116; Fri, 26 Apr 2019 00:00:05 -0700 (PDT) MIME-Version: 1.0 References: <20190424101934.51535-1-duyuyang@gmail.com> <20190425185641.GT12232@hirez.programming.kicks-ass.net> In-Reply-To: <20190425185641.GT12232@hirez.programming.kicks-ass.net> From: Yuyang Du Date: Fri, 26 Apr 2019 14:59:31 +0800 Message-ID: Subject: Re: [PATCH 00/28] Optimize IRQ usage checks and other small bits To: Peter Zijlstra Cc: will.deacon@arm.com, Ingo Molnar , Bart Van Assche , ming.lei@redhat.com, Frederic Weisbecker , tglx@linutronix.de, LKML 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 Thanks for review. On Fri, 26 Apr 2019 at 02:56, Peter Zijlstra wrote: > > On Wed, Apr 24, 2019 at 06:19:06PM +0800, Yuyang Du wrote: > > Yuyang Du (28): > > locking/lockdep: Change all print_*() return type to void > > locking/lockdep: Add description and explanation in lockdep design doc > > locking/lockdep: Adjust lock usage bit character checks > > locking/lockdep: Remove useless conditional macro > > locking/lockdep: Print the right depth for chain key colission > > locking/lockdep: Update obsolete struct field description > > locking/lockdep: Use lockdep_init_task for task initiation > > consistently > > locking/lockdep: Define INITIAL_CHAIN_KEY for chain keys to start with > > locking/lockdep: Change the range of class_idx in held_lock struct > > locking/lockdep: Remove unused argument in validate_chain() and > > check_deadlock() > > locking/lockdep: Update comment > > locking/lockdep: Change type of the element field in circular_queue > > locking/lockdep: Change the return type of __cq_dequeue() > > locking/lockdep: Avoid constant checks in __bfs by using offset > > reference > > locking/lockdep: Update comments on dependency search > > locking/lockdep: Add explanation to lock usage rules in lockdep design > > doc > > locking/lockdep: Remove redundant argument in check_deadlock > > locking/lockdep: Remove unused argument in __lock_release > > Those look really good (but don't readily apply to tip/locking/core) now > let me try and look at the real changes.. Swell.