From: Michael Ellerman <mpe@ellerman.id.au>
To: Michael Ellerman <patch-notifications@ellerman.id.au>,
Vaidyanathan Srinivasan <svaidy@linux.vnet.ibm.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Michal Suchanek <msuchanek@suse.de>,
"Gautham R. Shenoy" <ego@linux.vnet.ibm.com>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>,
Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: linux-pm@vger.kernel.org, joedecke@de.ibm.com,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v5 0/2] cpuidle/pseries: cleanup of the CEDE0 latency fixup code
Date: Tue, 03 Aug 2021 22:50:28 +1000 [thread overview]
Message-ID: <87o8aeofor.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <162798602812.163057.13114310314725073045.b4-ty@ellerman.id.au>
Michael Ellerman <patch-notifications@ellerman.id.au> writes:
> On Mon, 19 Jul 2021 12:03:17 +0530, Gautham R. Shenoy wrote:
>>
>> Hi,
>>
>> This is the v5 of the patchset to fixup CEDE0 latency only from
>> POWER10 onwards.
>>
>>
>> [...]
>
> Applied to powerpc/next.
>
> [1/2] cpuidle/pseries: Fixup CEDE0 latency only for POWER10 onwards
> https://git.kernel.org/powerpc/c/7cbd631d4decfd78f8a17196dce9abcd4e7e1e94
> [2/2] cpuidle/pseries: Do not cap the CEDE0 latency in fixup_cede0_latency()
> https://git.kernel.org/powerpc/c/4bceb03859c1a508669ce542c649c8d4f5d4bd93
First commit had a bad fixes tag, so now these are:
[1/2] cpuidle/pseries: Fixup CEDE0 latency only for POWER10 onwards
https://git.kernel.org/powerpc/c/50741b70b0cbbafbd9199f5180e66c0c53783a4a
[2/2] cpuidle/pseries: Do not cap the CEDE0 latency in fixup_cede0_latency()
https://git.kernel.org/powerpc/c/71737a6c2a8f801622d2b71567d1ec1e4c5b40b8
cheers
WARNING: multiple messages have this Message-ID (diff)
From: Michael Ellerman <mpe@ellerman.id.au>
To: Michael Ellerman <patch-notifications@ellerman.id.au>,
Vaidyanathan Srinivasan <svaidy@linux.vnet.ibm.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Michal Suchanek <msuchanek@suse.de>,
"Gautham R. Shenoy" <ego@linux.vnet.ibm.com>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>,
Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: linuxppc-dev@lists.ozlabs.org, joedecke@de.ibm.com,
linux-pm@vger.kernel.org
Subject: Re: [PATCH v5 0/2] cpuidle/pseries: cleanup of the CEDE0 latency fixup code
Date: Tue, 03 Aug 2021 22:50:28 +1000 [thread overview]
Message-ID: <87o8aeofor.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <162798602812.163057.13114310314725073045.b4-ty@ellerman.id.au>
Michael Ellerman <patch-notifications@ellerman.id.au> writes:
> On Mon, 19 Jul 2021 12:03:17 +0530, Gautham R. Shenoy wrote:
>>
>> Hi,
>>
>> This is the v5 of the patchset to fixup CEDE0 latency only from
>> POWER10 onwards.
>>
>>
>> [...]
>
> Applied to powerpc/next.
>
> [1/2] cpuidle/pseries: Fixup CEDE0 latency only for POWER10 onwards
> https://git.kernel.org/powerpc/c/7cbd631d4decfd78f8a17196dce9abcd4e7e1e94
> [2/2] cpuidle/pseries: Do not cap the CEDE0 latency in fixup_cede0_latency()
> https://git.kernel.org/powerpc/c/4bceb03859c1a508669ce542c649c8d4f5d4bd93
First commit had a bad fixes tag, so now these are:
[1/2] cpuidle/pseries: Fixup CEDE0 latency only for POWER10 onwards
https://git.kernel.org/powerpc/c/50741b70b0cbbafbd9199f5180e66c0c53783a4a
[2/2] cpuidle/pseries: Do not cap the CEDE0 latency in fixup_cede0_latency()
https://git.kernel.org/powerpc/c/71737a6c2a8f801622d2b71567d1ec1e4c5b40b8
cheers
next prev parent reply other threads:[~2021-08-03 12:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-19 6:33 [PATCH v5 0/2] cpuidle/pseries: cleanup of the CEDE0 latency fixup code Gautham R. Shenoy
2021-07-19 6:33 ` Gautham R. Shenoy
2021-07-19 6:33 ` [PATCH v5 1/2] cpuidle/pseries: Fixup CEDE0 latency only for POWER10 onwards Gautham R. Shenoy
2021-07-19 6:33 ` Gautham R. Shenoy
2021-07-19 6:33 ` [PATCH v5 2/2] cpuidle/pseries: Do not cap the CEDE0 latency in fixup_cede0_latency() Gautham R. Shenoy
2021-07-19 6:33 ` Gautham R. Shenoy
2021-08-03 10:20 ` [PATCH v5 0/2] cpuidle/pseries: cleanup of the CEDE0 latency fixup code Michael Ellerman
2021-08-03 10:20 ` Michael Ellerman
2021-08-03 12:50 ` Michael Ellerman [this message]
2021-08-03 12:50 ` Michael Ellerman
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=87o8aeofor.fsf@mpe.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=aneesh.kumar@linux.ibm.com \
--cc=daniel.lezcano@linaro.org \
--cc=ego@linux.vnet.ibm.com \
--cc=joedecke@de.ibm.com \
--cc=linux-pm@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=msuchanek@suse.de \
--cc=patch-notifications@ellerman.id.au \
--cc=rjw@rjwysocki.net \
--cc=svaidy@linux.vnet.ibm.com \
/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.