From: Meng Xu <mengxu@cis.upenn.edu>
To: xen-devel@lists.xen.org
Cc: wei.liu2@citrix.com, george.dunlap@eu.citrix.com,
dario.faggioli@citrix.com, ian.jackson@eu.citrix.com,
xumengpanda@gmail.com, Meng Xu <mengxu@cis.upenn.edu>
Subject: [PATCH v4 5/5] docs: enable per-VCPU extratime flag for RTDS
Date: Wed, 11 Oct 2017 14:02:06 -0400 [thread overview]
Message-ID: <1507744926-3950-6-git-send-email-mengxu@cis.upenn.edu> (raw)
In-Reply-To: <1507744926-3950-1-git-send-email-mengxu@cis.upenn.edu>
Revise xl tool use case by adding -e option
Remove work-conserving from TODO list
Signed-off-by: Meng Xu <mengxu@cis.upenn.edu>
Reviewed-by: Dario Faggioli <raistlin@linux.it>
Acked-by: Wei Liu <wei.liu2@citrix.com>
---
No change from v2
Changes from v1
Revise rtds docs
---
docs/features/sched_rtds.pandoc | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/docs/features/sched_rtds.pandoc b/docs/features/sched_rtds.pandoc
index 354097b..d51b499 100644
--- a/docs/features/sched_rtds.pandoc
+++ b/docs/features/sched_rtds.pandoc
@@ -40,7 +40,7 @@ as follows:
It is possible, for a multiple vCPUs VM, to change the parameters of
each vCPU individually:
- * `xl sched-rtds -d vm-rt -v 0 -p 20000 -b 10000 -v 1 -p 45000 -b 12000`
+ * `xl sched-rtds -d vm-rt -v 0 -p 20000 -b 10000 -e 1 -v 1 -p 45000 -b 12000 -e 0`
# Technical details
@@ -53,7 +53,8 @@ the presence of the LIBXL\_HAVE\_SCHED\_RTDS symbol. The ability of
specifying different scheduling parameters for each vcpu has been
introduced later, and is available if the following symbols are defined:
* `LIBXL\_HAVE\_VCPU\_SCHED\_PARAMS`,
- * `LIBXL\_HAVE\_SCHED\_RTDS\_VCPU\_PARAMS`.
+ * `LIBXL\_HAVE\_SCHED\_RTDS\_VCPU\_PARAMS`,
+ * `LIBXL\_HAVE\_SCHED\_RTDS\_VCPU\_EXTRA`.
# Limitations
@@ -95,7 +96,6 @@ at a macroscopic level), the following should be done:
# Areas for improvement
-* Work-conserving mode to be added;
* performance assessment, especially focusing on what level of real-time
behavior the scheduler enables.
@@ -118,4 +118,5 @@ at a macroscopic level), the following should be done:
Date Revision Version Notes
---------- -------- -------- -------------------------------------------
2016-10-14 1 Xen 4.8 Document written
+2017-08-31 2 Xen 4.10 Revise for work conserving feature
---------- -------- -------- -------------------------------------------
--
1.9.1
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-10-11 18:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-11 18:02 [PATCH v4 0/5] Towards work-conserving RTDS Meng Xu
2017-10-11 18:02 ` [PATCH v4 1/5] xen:rtds: towards work conserving RTDS Meng Xu
2017-10-11 18:02 ` [PATCH v4 2/5] libxl: enable per-VCPU extratime flag for RTDS Meng Xu
2017-10-11 18:02 ` [PATCH v4 3/5] xl: " Meng Xu
2017-10-11 18:02 ` [PATCH v4 4/5] xentrace: " Meng Xu
2017-10-17 8:10 ` Dario Faggioli
2017-10-17 13:22 ` Meng Xu
2017-10-23 18:50 ` Meng Xu
2017-10-25 14:31 ` Wei Liu
2017-11-02 13:49 ` Meng Xu
2017-11-16 16:30 ` Meng Xu
2017-10-11 18:02 ` Meng Xu [this message]
2017-10-12 9:02 ` [PATCH v4 0/5] Towards work-conserving RTDS Wei Liu
2017-10-12 14:34 ` Meng Xu
2017-10-17 7:26 ` Dario Faggioli
2017-10-17 7:29 ` Dario Faggioli
2017-10-17 13:19 ` Meng Xu
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=1507744926-3950-6-git-send-email-mengxu@cis.upenn.edu \
--to=mengxu@cis.upenn.edu \
--cc=dario.faggioli@citrix.com \
--cc=george.dunlap@eu.citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.org \
--cc=xumengpanda@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;
as well as URLs for NNTP newsgroup(s).