From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Xen-devel <xen-devel@lists.xen.org>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Ian Campbell <Ian.Campbell@citrix.com>
Subject: [Patch v3] docs: Correct docs for extra_guest_irqs command line option
Date: Wed, 31 Jul 2013 14:48:11 +0100 [thread overview]
Message-ID: <1375278491-14255-1-git-send-email-andrew.cooper3@citrix.com> (raw)
Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
CC: Ian Campbell <Ian.Campbell@citrix.com>
CC: Ian Jackson <Ian.Jackson@eu.citrix.com>
---
Changes for v3:
* Further clarification
Changes for v2:
* Spelling
* Clarification about the effects of optional parameters
---
docs/misc/xen-command-line.markdown | 10 ++++++++--
1 file changed, 8 insertions(+), 2 deletions(-)
diff --git a/docs/misc/xen-command-line.markdown b/docs/misc/xen-command-line.markdown
index 708ffc2..202d800 100644
--- a/docs/misc/xen-command-line.markdown
+++ b/docs/misc/xen-command-line.markdown
@@ -485,9 +485,15 @@ disable it (edid=no). This option should not normally be required
except for debugging purposes.
### extra\_guest\_irqs
-> `= <number>`
+> `= [<domU number>][,<dom0 number>]`
-Increase the number of PIRQs available for the guest. The default is 32.
+> Default: `32,256`
+
+Change the number of PIRQs available for guests. The optional first number is
+common for all domUs, while the optional second number (preceded by a comma)
+is for dom0. Changing the setting for domU has no impact on dom0 and vice
+versa. For example to change dom0 without changing domU, use
+`extra_guest_irqs=,512`
### flask\_enabled
> `= <integer>`
--
1.7.10.4
next reply other threads:[~2013-07-31 13:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-31 13:48 Andrew Cooper [this message]
2013-08-02 16:05 ` [Patch v3] docs: Correct docs for extra_guest_irqs command line option Ian Campbell
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=1375278491-14255-1-git-send-email-andrew.cooper3@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=xen-devel@lists.xen.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).