From: Jan Stancek <jstancek@redhat.com>
To: ltp-list@lists.sourceforge.net
Subject: [LTP] [PATCH 0/4 v2] (merged) cpuhotplug fixes
Date: Wed, 29 Apr 2015 13:17:57 +0200 [thread overview]
Message-ID: <cover.1430305546.git.jstancek@redhat.com> (raw)
Hi,
This patchset is result of merge of following series:
http://article.gmane.org/gmane.linux.ltp/22762
http://article.gmane.org/gmane.linux.ltp/22678
It is based on patchset from Stanislav, with changes
noted below:
1. cpuhotplug: use cpu states in cleanup
no changes to Stanislav's version
2. cpu_hotplug: added get_hotplug_cpus, get_hotplug_cpus_num
This patch has been merged with my 'get_present_cpus' patch,
get_hotplug_cpus has been modified to operate on present cpus
only.
3. cpu_hotplug: use hotplug/present cpus functions
This comes from my series, there is no counterpart or conflict
with Stanislav's patchset.
4. cpuhotplug04.sh: operate only with hotpluggable CPUs
minor change here to use number of present CPUs, rather than all
@Stanislav: Can you please review this series and check, whether
it still fixes issue you met on sparc64 kernel?
Regards,
Jan
Jan Stancek (1):
cpu_hotplug: use hotplug/present cpus functions
Stanislav Kholmanskikh (3):
cpuhotplug: use cpu states in cleanup
cpu_hotplug: add get_hotplug_cpus, get_present_cpus
cpuhotplug04.sh: operate only with hotpluggable CPUs
.../hotplug/cpu_hotplug/functional/cpuhotplug01.sh | 17 ++---
.../hotplug/cpu_hotplug/functional/cpuhotplug02.sh | 2 +-
.../hotplug/cpu_hotplug/functional/cpuhotplug03.sh | 16 ++--
.../hotplug/cpu_hotplug/functional/cpuhotplug04.sh | 74 +++++++++---------
.../hotplug/cpu_hotplug/functional/cpuhotplug05.sh | 2 +-
.../hotplug/cpu_hotplug/functional/cpuhotplug06.sh | 2 +-
.../hotplug/cpu_hotplug/functional/cpuhotplug07.sh | 2 +-
.../cpu_hotplug/include/cpuhotplug_hotplug.sh | 89 +++++++++++++++++++---
8 files changed, 135 insertions(+), 69 deletions(-)
--
1.8.3.1
------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next reply other threads:[~2015-04-29 11:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-29 11:17 Jan Stancek [this message]
2015-04-29 11:17 ` [LTP] [PATCH 1/4] cpuhotplug: use cpu states in cleanup Jan Stancek
2015-04-29 11:17 ` [LTP] [PATCH 2/4] cpu_hotplug: add get_hotplug_cpus, get_present_cpus Jan Stancek
2015-04-29 12:56 ` Stanislav Kholmanskikh
2015-04-29 11:18 ` [LTP] [PATCH 3/4] cpu_hotplug: use hotplug/present cpus functions Jan Stancek
2015-04-29 13:09 ` Stanislav Kholmanskikh
2015-04-29 14:41 ` Jan Stancek
2015-04-29 15:03 ` Stanislav Kholmanskikh
2015-04-29 11:18 ` [LTP] [PATCH 4/4] cpuhotplug04.sh: operate only with hotpluggable CPUs Jan Stancek
2015-04-29 13:11 ` [LTP] [PATCH 0/4 v2] (merged) cpuhotplug fixes Stanislav Kholmanskikh
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=cover.1430305546.git.jstancek@redhat.com \
--to=jstancek@redhat.com \
--cc=ltp-list@lists.sourceforge.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox