From: Viresh Kumar <viresh.kumar@linaro.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: "Rafael Wysocki" <rjw@rjwysocki.net>,
"Borislav Petkov" <bp@alien8.de>,
"David S. Miller" <davem@davemloft.net>,
"H. Peter Anvin" <hpa@zytor.com>,
"Ingo Molnar" <mingo@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Radim Krčmář" <rkrcmar@redhat.com>,
"Russell King" <linux@armlinux.org.uk>,
"Thomas Gleixner" <tglx@linutronix.de>,
"the arch/x86 maintainers" <x86@kernel.org>,
"Linux PM" <linux-pm@vger.kernel.org>,
"Vincent Guittot" <vincent.guittot@linaro.org>,
kvm@vger.kernel.org,
"Linux ARM" <linux-arm-kernel@lists.infradead.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
sparclinux@vger.kernel.org
Subject: Re: [PATCH 0/7] cpufreq: Call transition notifier only once for each policy
Date: Thu, 14 Mar 2019 16:33:18 +0530 [thread overview]
Message-ID: <20190314110318.on5bfau32tjsxnuz@vireshk-i7> (raw)
In-Reply-To: <CAJZ5v0jiumt_nvhc3Bv_b94Xq22h5vTwDPeM1qo+6bzChn58FQ@mail.gmail.com>
On 14-03-19, 11:55, Rafael J. Wysocki wrote:
> On Thu, Mar 14, 2019 at 11:16 AM Viresh Kumar <viresh.kumar@linaro.org> wrote:
> But some of them need to combine the new cpumask with
> cpu_online_mask() to get what would be policy->cpus effectively. That
> would be avoidable if you passed the policy pointer to them.
Right, that's what I also thought after your previous email. Will pass
the policy pointer instead.
--
viresh
WARNING: multiple messages have this Message-ID (diff)
From: Viresh Kumar <viresh.kumar@linaro.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: "Rafael Wysocki" <rjw@rjwysocki.net>,
"Borislav Petkov" <bp@alien8.de>,
"David S. Miller" <davem@davemloft.net>,
"H. Peter Anvin" <hpa@zytor.com>,
"Ingo Molnar" <mingo@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Radim Krčmář" <rkrcmar@redhat.com>,
"Russell King" <linux@armlinux.org.uk>,
"Thomas Gleixner" <tglx@linutronix.de>,
"the arch/x86 maintainers" <x86@kernel.org>,
"Linux PM" <linux-pm@vger.kernel.org>,
"Vincent Guittot" <vincent.guittot@linaro.org>,
kvm@vger.kernel.org,
"Linux ARM" <linux-arm-kernel@lists.infradead.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
sparclinux@vger.kernel.org
Subject: Re: [PATCH 0/7] cpufreq: Call transition notifier only once for each policy
Date: Thu, 14 Mar 2019 11:15:18 +0000 [thread overview]
Message-ID: <20190314110318.on5bfau32tjsxnuz@vireshk-i7> (raw)
In-Reply-To: <CAJZ5v0jiumt_nvhc3Bv_b94Xq22h5vTwDPeM1qo+6bzChn58FQ@mail.gmail.com>
On 14-03-19, 11:55, Rafael J. Wysocki wrote:
> On Thu, Mar 14, 2019 at 11:16 AM Viresh Kumar <viresh.kumar@linaro.org> wrote:
> But some of them need to combine the new cpumask with
> cpu_online_mask() to get what would be policy->cpus effectively. That
> would be avoidable if you passed the policy pointer to them.
Right, that's what I also thought after your previous email. Will pass
the policy pointer instead.
--
viresh
WARNING: multiple messages have this Message-ID (diff)
From: Viresh Kumar <viresh.kumar@linaro.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: "Vincent Guittot" <vincent.guittot@linaro.org>,
kvm@vger.kernel.org, "Radim Krčmář" <rkrcmar@redhat.com>,
"Linux PM" <linux-pm@vger.kernel.org>,
"the arch/x86 maintainers" <x86@kernel.org>,
"Rafael Wysocki" <rjw@rjwysocki.net>,
"Russell King" <linux@armlinux.org.uk>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Ingo Molnar" <mingo@redhat.com>,
"Borislav Petkov" <bp@alien8.de>,
"H. Peter Anvin" <hpa@zytor.com>,
sparclinux@vger.kernel.org, "Paolo Bonzini" <pbonzini@redhat.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
"David S. Miller" <davem@davemloft.net>,
"Linux ARM" <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 0/7] cpufreq: Call transition notifier only once for each policy
Date: Thu, 14 Mar 2019 16:33:18 +0530 [thread overview]
Message-ID: <20190314110318.on5bfau32tjsxnuz@vireshk-i7> (raw)
In-Reply-To: <CAJZ5v0jiumt_nvhc3Bv_b94Xq22h5vTwDPeM1qo+6bzChn58FQ@mail.gmail.com>
On 14-03-19, 11:55, Rafael J. Wysocki wrote:
> On Thu, Mar 14, 2019 at 11:16 AM Viresh Kumar <viresh.kumar@linaro.org> wrote:
> But some of them need to combine the new cpumask with
> cpu_online_mask() to get what would be policy->cpus effectively. That
> would be avoidable if you passed the policy pointer to them.
Right, that's what I also thought after your previous email. Will pass
the policy pointer instead.
--
viresh
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-03-14 11:03 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-14 6:42 [PATCH 0/7] cpufreq: Call transition notifier only once for each policy Viresh Kumar
2019-03-14 6:54 ` Viresh Kumar
2019-03-14 6:42 ` Viresh Kumar
2019-03-14 6:42 ` [PATCH 1/7] cpufreq: Pass policy->related_cpus to transition notifiers Viresh Kumar
2019-03-14 6:42 ` [PATCH 2/7] ARM: smp: Update cpufreq transition notifier to handle multiple CPUs Viresh Kumar
2019-03-14 6:42 ` Viresh Kumar
2019-03-14 6:42 ` [PATCH 3/7] ARM: twd: " Viresh Kumar
2019-03-14 6:42 ` Viresh Kumar
2019-03-14 6:42 ` [PATCH 4/7] sparc64: " Viresh Kumar
2019-03-14 6:54 ` Viresh Kumar
2019-03-14 17:27 ` David Miller
2019-03-14 17:27 ` David Miller
2019-03-14 6:42 ` [PATCH 5/7] x86/tsc: " Viresh Kumar
2019-03-14 9:33 ` Rafael J. Wysocki
2019-03-14 10:03 ` Viresh Kumar
2019-03-14 6:42 ` [PATCH 6/7] KVM: x86: " Viresh Kumar
2019-03-14 6:42 ` [PATCH 7/7] cpufreq: Call transition notifiers only once for each policy Viresh Kumar
2019-03-14 9:28 ` [PATCH 0/7] cpufreq: Call transition notifier " Rafael J. Wysocki
2019-03-14 9:28 ` Rafael J. Wysocki
2019-03-14 9:28 ` Rafael J. Wysocki
2019-03-14 9:28 ` Rafael J. Wysocki
2019-03-14 9:40 ` Rafael J. Wysocki
2019-03-14 9:40 ` Rafael J. Wysocki
2019-03-14 9:40 ` Rafael J. Wysocki
2019-03-14 10:18 ` Viresh Kumar
2019-03-14 10:30 ` Viresh Kumar
2019-03-14 10:18 ` Viresh Kumar
2019-03-14 10:16 ` Viresh Kumar
2019-03-14 10:28 ` Viresh Kumar
2019-03-14 10:16 ` Viresh Kumar
2019-03-14 10:55 ` Rafael J. Wysocki
2019-03-14 10:55 ` Rafael J. Wysocki
2019-03-14 10:55 ` Rafael J. Wysocki
2019-03-14 11:03 ` Viresh Kumar [this message]
2019-03-14 11:15 ` Viresh Kumar
2019-03-14 11:03 ` Viresh Kumar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190314110318.on5bfau32tjsxnuz@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=bp@alien8.de \
--cc=davem@davemloft.net \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
--cc=rkrcmar@redhat.com \
--cc=sparclinux@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=vincent.guittot@linaro.org \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.