From: Andrii Anisov <andrii_anisov@epam.com>
To: Meng Xu <xumengpanda@gmail.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: RT-Xen on ARM
Date: Wed, 27 Sep 2017 17:37:42 +0300 [thread overview]
Message-ID: <20e4bb06-ae29-266c-2d09-83cee826a29d@epam.com> (raw)
In-Reply-To: <CAENZ-+kRpAmbavY6=10O7HDwgsnDq-75JfVGO_X5=Ji_UuSa4A@mail.gmail.com>
Hello,
On 27.09.17 16:57, Meng Xu wrote:
> The command is:
> java -jar carts.jar inputfile outputfile
From the next example, I would say the command is:
java -jar carts.jar inputfile interface_type outputfile
> An example command is:
> java -jar carts.jar 1-1.10-in.xml MPR2 1-1.10-out.xml
Thanks a lot. It does work.
Could you please clarify a bit more points to me:
- As I understand the upstreamed rtds employs gEDF only. Is it
correct?
- Could you please provide an example input xml for CARTS described
a system with 2 RT domains with 2 VCPUs each, running on a 2PCPUs, with
gEDF scheduling at VMM level (for XEN based setup). For pEDF at both VMM
and domain level, my understanding is that the os_scheduler represents
XEN, and VCPUs are represented by components with tasks running on them.
- I did not get a concept of min_period/max_period for a
component/os_scheduler in CARTS description files. If I have them
different, CARTS gives calculation for all periods in between, but did
not provide the best period to get system schedulable.
--
*Andrii Anisov*
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-09-27 14:37 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-03 11:03 RT-Xen on ARM Andrii Anisov
2017-07-03 13:03 ` Wei Liu
2017-07-03 13:26 ` Andrii Anisov
2017-07-03 13:35 ` Meng Xu
2017-07-03 14:58 ` Andrii Anisov
2017-07-03 18:42 ` Meng Xu
2017-07-04 12:28 ` Andrii Anisov
2017-07-04 15:12 ` Meng Xu
2017-07-05 8:29 ` Dario Faggioli
2017-07-07 18:29 ` Meng Xu
2017-07-12 6:13 ` Dario Faggioli
2017-07-05 8:42 ` Dario Faggioli
2017-07-05 8:51 ` Dario Faggioli
2017-07-07 18:43 ` Meng Xu
2017-07-07 18:46 ` Meng Xu
2017-07-10 9:22 ` Andrii Anisov
2017-08-01 11:02 ` Andrii Anisov
2017-08-18 20:43 ` Meng Xu
2017-08-21 8:07 ` Andrii Anisov
2017-08-21 8:16 ` Andrii Anisov
2017-08-22 2:02 ` Meng Xu
2017-09-27 12:37 ` Andrii Anisov
2017-09-27 13:57 ` Meng Xu
2017-09-27 14:37 ` Andrii Anisov [this message]
2017-09-27 19:57 ` Meng Xu
2017-09-28 9:18 ` Andrii Anisov
2017-09-28 16:01 ` Dario Faggioli
2017-09-28 17:56 ` Dario Faggioli
2017-09-29 10:24 ` Andrii Anisov
2017-10-09 15:38 ` Meng Xu
2017-08-22 1:58 ` Meng Xu
2017-08-21 8:38 ` Andrii Anisov
2017-08-22 2:19 ` Meng Xu
2017-07-05 7:33 ` Dario Faggioli
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=20e4bb06-ae29-266c-2d09-83cee826a29d@epam.com \
--to=andrii_anisov@epam.com \
--cc=xen-devel@lists.xenproject.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 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.