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 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 10C4EC433FE for ; Thu, 11 Nov 2021 16:32:52 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id E694661252 for ; Thu, 11 Nov 2021 16:32:51 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234175AbhKKQfk (ORCPT ); Thu, 11 Nov 2021 11:35:40 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:57066 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233966AbhKKQfj (ORCPT ); Thu, 11 Nov 2021 11:35:39 -0500 Received: from mail-pl1-x632.google.com (mail-pl1-x632.google.com [IPv6:2607:f8b0:4864:20::632]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 95225C061766 for ; Thu, 11 Nov 2021 08:32:50 -0800 (PST) Received: by mail-pl1-x632.google.com with SMTP id y7so6303353plp.0 for ; Thu, 11 Nov 2021 08:32:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=H1yErXT4EpwpUbhpshtUdMiS4figBQYN9WRkNajA+aw=; b=iP+Te/2AarqvwmfzBqyhFxvKJcHUaPp0nZJw9QWNBt0F1dhshBB/cM9Q304a2syyxx NeRsxgbuPOhhtRlxksRi59BDIRYQ6QVYIdW1CaANk0G1ZEhOH16OaDHbaWm2qIuSWvB9 eKb9IaoRiD7jcd46Vho+gJClp5ndQ4DKhvV5I= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=H1yErXT4EpwpUbhpshtUdMiS4figBQYN9WRkNajA+aw=; b=pcWk4fCZ6wdCGtYe+Cnw+emKPELXdKZUzZPRavy6d4AVZZLqKiDvFoARPDNFkZ4Etq N15HdJCFep7YdLd6iFD33RuAfWqlGO9al5wuD/SQk2a50pR0Sge7HEyqS2XDsODYTtCK eoQhssDF2B2Jd3Jgfk9RdslKTg7yRwTKmvWqhNojlCCy83mYT8VL2MkSmn8ZpEdSRHgi W8IEWwHiI3j7jfVafeNkTGxKhdbBkCrpJA6W/XAwO0KlXtu5W7Rpv19mF0vkrpVh6c4Y AERWZZEpbVjWflbkNpV44MNFWqMOZVuUp5nTn2G37fdDR7WT4C6wmHOMeoUa1G8/39hw T75A== X-Gm-Message-State: AOAM5326Vn0DD2zE2ImpZDqV6ioTuIT97t4ZjqpVCoiLgIA91a292ND9 cRYbnMtyEg7qYtWIelfiyrDqGA== X-Google-Smtp-Source: ABdhPJzXVf/0jnwa3cU1jIOBMG995/y5rYDNfR81sGfUqxxzlAWg6KQWTHL7MkfPvgAm9EunKKgUeQ== X-Received: by 2002:a17:90b:4d0f:: with SMTP id mw15mr27671616pjb.0.1636648370062; Thu, 11 Nov 2021 08:32:50 -0800 (PST) Received: from localhost ([2620:15c:202:201:c0a9:ac53:7829:6af7]) by smtp.gmail.com with UTF8SMTPSA id q10sm7691514pjd.0.2021.11.11.08.32.49 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 11 Nov 2021 08:32:49 -0800 (PST) Date: Thu, 11 Nov 2021 08:32:48 -0800 From: Matthias Kaehlcke To: Vladimir Zapolskiy Cc: Viresh Kumar , "Rafael J. Wysocki" , Thara Gopinath , Bjorn Andersson , linux-arm-msm@vger.kernel.org, linux-pm@vger.kernel.org Subject: Re: [PATCH 3/3] cpufreq: qcom-hw: Set CPU affinity of dcvsh interrupts Message-ID: References: <20211111154808.2024808-1-vladimir.zapolskiy@linaro.org> <20211111154808.2024808-4-vladimir.zapolskiy@linaro.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20211111154808.2024808-4-vladimir.zapolskiy@linaro.org> Precedence: bulk List-ID: X-Mailing-List: linux-pm@vger.kernel.org On Thu, Nov 11, 2021 at 05:48:08PM +0200, Vladimir Zapolskiy wrote: > In runtime CPU cluster specific dcvsh interrupts may be handled on > unrelated CPU cores, it leads to an issue of too excessive number of > received and handled interrupts, but this is not observed, if CPU > affinity of the interrupt handler is set in accordance to CPU clusters. > > The change reduces a number of received interrupts in about 10-100 times. > > Signed-off-by: Vladimir Zapolskiy Reviewed-by: Matthias Kaehlcke