All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Richard W.M. Jones" <rjones@redhat.com>
To: xen-devel@lists.xensource.com
Subject: [PATCH] Clarify use of xm mem-set and xm vcpu-set in xm.1 manpage
Date: Thu, 17 Jan 2008 17:24:16 +0000	[thread overview]
Message-ID: <478F8F40.9090304@redhat.com> (raw)


[-- Attachment #1.1.1: Type: text/plain, Size: 456 bytes --]

'xm mem-set' and 'xm vcpu-set' require cooperation of the domain.  This 
patch just clarifies the xm.1 manpage to make it clear that the commands 
won't work on a purely fullvirt domain.

Rich.

-- 
Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/
Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod
Street, Windsor, Berkshire, SL4 1TE, United Kingdom.  Registered in
England and Wales under Company Registration No. 03798903

[-- Attachment #1.1.2: xen-unstable-clarify-mem-set-vcpu-set.patch --]
[-- Type: text/x-patch, Size: 1286 bytes --]

diff -r f17b34df974f docs/man/xm.pod.1
--- a/docs/man/xm.pod.1	Wed Jan 16 15:55:57 2008 +0000
+++ b/docs/man/xm.pod.1	Thu Jan 17 17:21:23 2008 +0000
@@ -254,9 +254,12 @@ domain, as it may balloon down its memor
 
 =item B<mem-set> I<domain-id> I<mem>
 
-Set the domain's used memory using the balloon driver.  Because this
-operation requires cooperation from the domain operating system, there
-is no guarantee that it will succeed.
+Set the domain's used memory using the balloon driver.
+
+Because this operation requires cooperation from the domain operating
+system, there is no guarantee that it will succeed.  This command will
+definitely not work unless the domain has the required paravirt
+driver.
 
 B<Warning:> There is no good way to know in advance how small of a
 mem-set will make a domain unstable and cause it to crash.  Be very
@@ -391,6 +394,10 @@ Attempting to set the VCPUs to a number 
 Attempting to set the VCPUs to a number larger than the initially
 configured VCPU count is an error.  Trying to set VCPUs to < 1 will be
 quietly ignored.
+
+Because this operation requires cooperation from the domain operating
+system, there is no guarantee that it will succeed.  This command will
+not work with a full virt domain.
 
 =item B<vcpu-list> [I<domain-id>]
 

[-- Attachment #1.2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3237 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

                 reply	other threads:[~2008-01-17 17:24 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=478F8F40.9090304@redhat.com \
    --to=rjones@redhat.com \
    --cc=xen-devel@lists.xensource.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.