All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: Karel Zak <kzak@redhat.com>,
	util-linux@vger.kernel.org,
	Gerald Schaefer <gerald.schaefer@de.ibm.com>
Subject: Re: [PATCH 3/4] chmem: new tool
Date: Wed, 19 Oct 2016 12:40:33 +0200	[thread overview]
Message-ID: <20161019104033.GG4077@osiris> (raw)
In-Reply-To: <20161012120047.60732-4-heiko.carstens@de.ibm.com>

On Wed, Oct 12, 2016 at 02:00:46PM +0200, Heiko Carstens wrote:
> Move the s390 specific chmem tool to util-linux.
> 
> The chmem tool was originally written in perl and is part of the
> s390-tools package which can be found here:
> https://www.ibm.com/developerworks/linux/linux390/s390-tools.html
> 
> Given that the tool is architecture independent, there is no reason to
> keep it in an s390 specific repository. It seems to be useful for
> other architectures as well.
> 
> This patch converts the tool to C and adds it to util-linux, while the
> command line options stay compatible. The only exception is the option
> "-v" which used to be the short form of "--version". That got changed
> to "-V" so it behaves like most other tools contained within
> util-linux.
> 
> The chmem tool can be used to set memory online or offline. This can
> be achieved by specifying a memory range:
> 
> Memory Block 19 (0x0000000130000000-0x000000013fffffff) disabled
> 
> or by specifying a size where chmem will automatically select memory
> blocks:
> 
> Memory Block 21 (0x0000000150000000-0x000000015fffffff) disable failed
> Memory Block 18 (0x0000000120000000-0x000000012fffffff) disabled
> Memory Block 17 (0x0000000110000000-0x000000011fffffff) disabled
> Memory Block 16 (0x0000000100000000-0x000000010fffffff) disabled
> Memory Block 15 (0x00000000f0000000-0x00000000ffffffff) disabled
> 
> or by specifying memory block numbers instead of address ranges:
> 
> Memory Block 15 (0x00000000f0000000-0x00000000ffffffff) disabled
> Memory Block 16 (0x0000000100000000-0x000000010fffffff) disabled
> Memory Block 17 (0x0000000110000000-0x000000011fffffff) disabled
> Memory Block 18 (0x0000000120000000-0x000000012fffffff) disabled
> 
> This is based on a patch from Clemens von Mann.
> 
> Signed-off-by: Heiko Carstens <heiko.carstens@de.ibm.com>

I just realized that the above "examples" don't make sense, since the
commands that were used are missing. That happened because I started the
lines with "#", which apparently git assumed to be a comment and therefore
ignored the lines.

So the correct description, which contains the commands, should be:

> The chmem tool can be used to set memory online or offline. This can
> be achieved by specifying a memory range:
>
> $ chmem -v -d 0x0000000130000000-0x000000013fffffff
> Memory Block 19 (0x0000000130000000-0x000000013fffffff) disabled
>
> or by specifying a size where chmem will automatically select memory
> blocks:
>
> $ chmem -v -d  1g
> Memory Block 21 (0x0000000150000000-0x000000015fffffff) disable failed
> Memory Block 18 (0x0000000120000000-0x000000012fffffff) disabled
> Memory Block 17 (0x0000000110000000-0x000000011fffffff) disabled
> Memory Block 16 (0x0000000100000000-0x000000010fffffff) disabled
> Memory Block 15 (0x00000000f0000000-0x00000000ffffffff) disabled
>
> or by specifying memory block numbers instead of address ranges:
>
> $ chmem -v -d -b 15-18
> Memory Block 15 (0x00000000f0000000-0x00000000ffffffff) disabled
> Memory Block 16 (0x0000000100000000-0x000000010fffffff) disabled
> Memory Block 17 (0x0000000110000000-0x000000011fffffff) disabled
> Memory Block 18 (0x0000000120000000-0x000000012fffffff) disabled


  reply	other threads:[~2016-10-19 14:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-12 12:00 [PATCH 0/4] New tools lsmem and chmem Heiko Carstens
2016-10-12 12:00 ` [PATCH 1/4] lib,strutils: add strtoux[16|32|64]_or_err functions Heiko Carstens
2016-10-12 12:00 ` [PATCH 2/4] lsmem: new tool Heiko Carstens
2016-11-03 12:00   ` Karel Zak
2016-11-03 16:19     ` Heiko Carstens
2016-11-04 10:39       ` Karel Zak
2016-11-04 12:10         ` Heiko Carstens
2016-11-09  9:16           ` Karel Zak
2016-10-12 12:00 ` [PATCH 3/4] chmem: " Heiko Carstens
2016-10-19 10:40   ` Heiko Carstens [this message]
2016-10-12 12:00 ` [PATCH 4/4] lsmem: add testcase Heiko Carstens
2016-10-19  9:38 ` [PATCH 0/4] New tools lsmem and chmem Karel Zak
2016-10-19  9:59   ` Heiko Carstens

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=20161019104033.GG4077@osiris \
    --to=heiko.carstens@de.ibm.com \
    --cc=gerald.schaefer@de.ibm.com \
    --cc=kzak@redhat.com \
    --cc=util-linux@vger.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.