public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Asias He <asias.hejun@gmail.com>
To: Pekka Enberg <penberg@kernel.org>
Cc: kvm@vger.kernel.org, Avi Kivity <avi@redhat.com>,
	Cyrill Gorcunov <gorcunov@gmail.com>, Ingo Molnar <mingo@elte.hu>,
	Prasad Joshi <prasadjoshi124@gmail.com>,
	Sasha Levin <levinsasha928@gmail.com>
Subject: Re: [PATCH 1/2] kvm tools: Use '-c' for '--cpus', not '--console'
Date: Thu, 12 May 2011 09:09:10 +0800	[thread overview]
Message-ID: <4DCB3336.5060401@gmail.com> (raw)
In-Reply-To: <1305136906-14496-1-git-send-email-penberg@kernel.org>

On 05/12/2011 02:01 AM, Pekka Enberg wrote:
> This patch changes the '-c' command line option to specify the number of CPUs
> because it's used more often than console switching.

I'd like to tune the command line option further.

1)
Change
    -i, --image <image>   Disk image
to
    -d, --disk  <disk>	  Disk image
2)
Change
    -r, --initrd <initrd>
                          Initial RAM disk image
to
    -i, --initrd <initrd>
                          Initial RAM disk image
3)
Change
    -d, --kvm-dev <kvm-dev>
                          KVM device file
    -s, --single-step     Enable single stepping
    -g, --ioport-debug    Enable ioport debugging
to
        --kvm-dev <kvm-dev>
                          KVM device file
        --single-step     Enable single stepping
        --ioport-debug    Enable ioport debugging
.

So we can have
	-c --cpus
	-m --mem
	-d --disk
	-k --kernel
	-i --initrd
which is more consistent and easy to remember.


-- 
Best Regards,
Asias He

  parent reply	other threads:[~2011-05-12  1:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-11 18:01 [PATCH 1/2] kvm tools: Use '-c' for '--cpus', not '--console' Pekka Enberg
2011-05-11 18:01 ` [PATCH 2/2] kvm tools: Print out important command line options at startup Pekka Enberg
2011-05-12  1:09 ` Asias He [this message]
2011-05-12  7:17   ` [PATCH 1/2] kvm tools: Use '-c' for '--cpus', not '--console' Ingo Molnar
2011-05-12 13:20     ` Asias He

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=4DCB3336.5060401@gmail.com \
    --to=asias.hejun@gmail.com \
    --cc=avi@redhat.com \
    --cc=gorcunov@gmail.com \
    --cc=kvm@vger.kernel.org \
    --cc=levinsasha928@gmail.com \
    --cc=mingo@elte.hu \
    --cc=penberg@kernel.org \
    --cc=prasadjoshi124@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox