From: Venu Busireddy <venu.busireddy@oracle.com>
To: venu.busireddy@oracle.comVenu Busireddy <venu.busireddy@oracle.com>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
Wei Liu <wei.liu2@citrix.com>,
George Dunlap <George.Dunlap@eu.citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>, Tim Deegan <tim@xen.org>,
Jan Beulich <jbeulich@suse.com>,
xen-devel@lists.xen.org
Subject: [PATCH] iommu: Elaborate the usage of RMRR specification on the command line.
Date: Tue, 21 Feb 2017 14:42:01 -0600 [thread overview]
Message-ID: <1487709721-18619-1-git-send-email-venu.busireddy@oracle.com> (raw)
As some users have suggested, elaborate the usage of RMRR specification
on the command line, and provide a usage example.
Signed-off-by: Venu Busireddy <venu.busireddy@oracle.com>
---
docs/misc/xen-command-line.markdown | 9 +++++++++
1 files changed, 9 insertions(+), 0 deletions(-)
diff --git a/docs/misc/xen-command-line.markdown b/docs/misc/xen-command-line.markdown
index 3acbb33..77e0a20 100644
--- a/docs/misc/xen-command-line.markdown
+++ b/docs/misc/xen-command-line.markdown
@@ -1406,6 +1406,15 @@ If segment of the first device is not specified, segment zero will be used.
If other segments are not specified, first device segment will be used.
If a segment is specified for other than the first device and it does not match
the one specified for the first one, an error will be reported.
+
+'start' and 'end' values are page numbers (not full physical addresses).
+If the values are not preceded by "0x", they are treated as decimal.
+
+Usage example: If there are two devices 0:0:1d.0 and 0:0:1a.0 that require
+pages 0xd5d45 and 0xd5d46 to be reserved respectively, use:
+
+rmrr=0xd5d45=0:0:1d.0;0xd5d46=0:0:1a.0
+
Note: grub2 requires to escape or use quotations if special characters are used,
namely ';', refer to the grub2 documentation if multiple ranges are specified.
--
1.7.1
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next reply other threads:[~2017-02-21 20:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-21 20:42 Venu Busireddy [this message]
2017-02-22 8:52 ` [PATCH] iommu: Elaborate the usage of RMRR specification on the command line Jan Beulich
2017-02-23 17:03 ` Venu Busireddy
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=1487709721-18619-1-git-send-email-venu.busireddy@oracle.com \
--to=venu.busireddy@oracle.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=sstabellini@kernel.org \
--cc=tim@xen.org \
--cc=venu.busireddy@oracle.comVenu \
--cc=wei.liu2@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).