From: Dario Faggioli <dario.faggioli@citrix.com>
To: Dagaen Golomb <dgolomb@seas.upenn.edu>
Cc: Sisu Xi <xisisu@gmail.com>,
George Dunlap <george.dunlap@eu.citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Meng Xu <xumengpanda@gmail.com>, Meng Xu <mengxu@cis.upenn.edu>,
Chong Li <lichong659@gmail.com>
Subject: Re: [PATCH v2] Modified RTDS scheduler to use an event-driven model instead of polling.
Date: Mon, 6 Jul 2015 19:41:32 +0200 [thread overview]
Message-ID: <1436204492.10763.46.camel@citrix.com> (raw)
In-Reply-To: <CALcuvTjnvnc_R+ra38PPA6mnpKZ-JkAZnVhh0gnUcsdKUJZ+0A@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1015 bytes --]
On Sun, 2015-06-28 at 16:17 -0400, Dagaen Golomb wrote:
> It does take some thinking as to whether this will occur or not. I
> also am not sure
> if Xen will let the timer handlers preempt each other and, if so, if
> this is even a
> problem.
>
I was about to tell you... But, really, if you want to try going there
and finding it yourself, I think it would be more useful, as you'll
learn something and you won't forget the answer after 5 minutes, as it
happens when someone just tells you something, without you knowing out
of own personal investigation, why that is the case. :-)
So, as you wish. If you just wanna know, as again. If you fancy go down
in the code and check, that, IMO, would be best. :-D
Thanks and 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: 181 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2015-07-06 17:41 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-27 19:46 [PATCH v2] Modified RTDS scheduler to use an event-driven model instead of polling Dagaen Golomb
2015-06-27 19:53 ` Dagaen Golomb
2015-06-28 7:10 ` Meng Xu
2015-06-28 17:49 ` Dagaen Golomb
2015-06-28 19:11 ` Meng Xu
2015-06-28 20:17 ` Dagaen Golomb
2015-06-28 20:45 ` Meng Xu
2015-07-06 17:37 ` Dario Faggioli
2015-07-06 17:41 ` Dario Faggioli [this message]
2015-07-09 16:19 ` Dagaen Golomb
2015-06-28 7:06 ` Meng Xu
2015-07-06 17:30 ` Dario Faggioli
2015-07-07 5:51 ` Meng Xu
2015-07-07 14:03 ` Dario Faggioli
2015-07-08 5:56 ` Meng Xu
2015-07-08 8:01 ` Dario Faggioli
2015-07-09 3:46 ` Meng Xu
2015-07-09 16:39 ` Dagaen Golomb
2015-07-10 10:07 ` Dario Faggioli
2015-07-09 16:35 ` Dagaen Golomb
2015-07-09 16:31 ` Dagaen Golomb
2015-07-09 16:17 ` Dagaen Golomb
-- strict thread matches above, loose matches on Subject: below --
2015-07-03 5:12 Meng Xu
2015-07-06 11:51 ` Dario Faggioli
2015-06-27 19:35 Dagaen Golomb
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=1436204492.10763.46.camel@citrix.com \
--to=dario.faggioli@citrix.com \
--cc=dgolomb@seas.upenn.edu \
--cc=george.dunlap@eu.citrix.com \
--cc=lichong659@gmail.com \
--cc=mengxu@cis.upenn.edu \
--cc=xen-devel@lists.xen.org \
--cc=xisisu@gmail.com \
--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).