From: Nate Studer <nate.studer@dornerworks.com>
To: Simon Martin <smartin@milliways.cl>,
Robbie VanVossen <robert.vanvossen@dornerworks.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Mapping shared pages from Windows
Date: Thu, 31 Oct 2013 14:19:09 -0400 [thread overview]
Message-ID: <52729F1D.2080505@dornerworks.com> (raw)
In-Reply-To: <em3f302c90-e0ce-465f-8326-607b5eba69e9@smartin-alien>
> At the moment my development is in the initial stages of learning the Xen
> infrastructure and how to push things around. I expect to be another couple of
> weeks experimenting with ways of doing things before I decide how this should be
> done. Like for instance setting up a CPU pool with the arinc653 scheduler seems
> to crash the hypervisor.
I just tried to repeat your issue and I get a crash in the credit scheduler!?
(XEN) Xen BUG at sched_credit.c:917
(XEN) ----[ Xen-4.4-unstable x86_64 debug=y Tainted: C ]----
(XEN) CPU: 0
(XEN) RIP: e008:[<ffff82d08011a30d>] csched_free_vdata+0x9/0x15
(XEN) RFLAGS: 0000000000010202 CONTEXT: hypervisor
If I create a pool with any scheduler other than arinc653, I do not see this
crash, so something is definitely not right.
I am pretty sure that this line in the arinc653 scheduler is the culprit.
if ( (vc->sched_priv = xmalloc(arinc653_vcpu_t)) == NULL )
>>
>> James
> Simon.
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
>
next prev parent reply other threads:[~2013-10-31 18:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-25 19:35 Mapping shared pages from Windows Simon Martin
2013-10-25 22:48 ` James Harper
2013-10-27 22:43 ` Simon Martin
2013-10-30 18:39 ` Nate Studer
2013-10-31 18:19 ` Nate Studer [this message]
2013-10-28 9:46 ` Paul Durrant
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=52729F1D.2080505@dornerworks.com \
--to=nate.studer@dornerworks.com \
--cc=robert.vanvossen@dornerworks.com \
--cc=smartin@milliways.cl \
--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 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.