From: Dario Faggioli <dario.faggioli@citrix.com>
To: Andrii Anisov <andrii_anisov@epam.com>, Meng Xu <mengxu@seas.upenn.edu>
Cc: xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: RT-Xen on ARM
Date: Wed, 5 Jul 2017 09:33:00 +0200 [thread overview]
Message-ID: <1499239980.7486.3.camel@citrix.com> (raw)
In-Reply-To: <b6de44dc-d4df-cda4-6a92-f39415bbc54f@epam.com>
[-- Attachment #1.1: Type: text/plain, Size: 1064 bytes --]
On Mon, 2017-07-03 at 14:03 +0300, Andrii Anisov wrote:
> - root@salvator-x-h3-xt:/scripts# xl sched-rtds -d DomU -v all -p
> 10000
> -b 2500
> (XEN) FLASK: Denying unknown domctl_scheduler_op: 2.
> libxl: error: libxl_sched.c:663:sched_rtds_vcpu_set_all: Domain
> 2:Setting vcpu sched rtds: Operation not permitted
> libxl_vcpu_sched_params_set_all failed.
>
Mmm... this looks to me to mean that we're missing the XSM/Flask bits
of XEN_DOMCTL_SCHEDOP_putvcpuinfo and XEN_DOMCTL_SCHEDOP_getvcpuinfo.
Meng, can you guys check (e.g., by building a Flask enabled hypervisor
and testing the basic functionalities of RTDS) and, if it actually does
not work, fix this?
It should be ok to test on x86, as I don't think this is something ARM
specific.
Regards,
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 127 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2017-07-05 7:33 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
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 [this message]
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=1499239980.7486.3.camel@citrix.com \
--to=dario.faggioli@citrix.com \
--cc=andrii_anisov@epam.com \
--cc=mengxu@seas.upenn.edu \
--cc=xen-devel@lists.xenproject.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).