xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Dario Faggioli <dario.faggioli@citrix.com>
To: Meng Xu <xumengpanda@gmail.com>
Cc: embedded-pv-devel <embedded-pv-devel@lists.xenproject.org>,
	Xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [Embedded-pv-devel] Xen Project Developer Summit : program Published
Date: Mon, 25 Jul 2016 12:50:20 +0200	[thread overview]
Message-ID: <1469443820.13039.306.camel@citrix.com> (raw)
In-Reply-To: <CAENZ-+ms+2zynN8ZXwqu=kCk1GGK_0bmfZyL6SsBJCCLy0j9-g@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1774 bytes --]

On Fri, 2016-07-15 at 10:56 -0400, Meng Xu wrote:
> On Fri, Jul 15, 2016 at 8:01 AM, Dario Faggioli
> <dario.faggioli@citrix.com> wrote:
> > 
> > * "Consideration of Real Time GPU Scheduling of XenGT in Automotive
> >    Embedded System"
> >   Sangyun Lee, LG Electronics http://sched.co/7Lh3
> > 
> > * "Xenbedded: Xen-based client virtualization for phones and
> > tablets"
> >   Chris Patterson & Kyle Temkin, AIS, Inc. http://sched.co/7LhI
> > 
> > * "Review and Analysis of Performance Metrics of the Xen Hypervisor
> > on
> >    Zynq UltraScale+ MPSoC"
> >    Jarvis Roach & Benjamin Sanda, DornerWorks http://sched.co/7Lh0
> > 
> > How cool is all that, eh?
>
> Very cool~ :-)
> 
:-)

> > We better continue to work on putting RTDS into as good as possible
> > shape... World may need it soon! :-P :-P
> Yes. I totally agree! One most important TODO for RTDS is to convert
> it from non-work-conserving model to work-conserving model. I have
> been keeping this in mind for a while. I can discuss this in our
> internal RT-Xen meeting and try to get a plan for this. 
> 
Yes, that would be one good thing.

> BTW, I may go to the summit if my Canada visa got approved on time. 
> Are you coming to the summit? 
> 
Not this year. So, if you go, responsibility of talking with (not
only!) these people, listen to their needs, and lobby in favour of RTDS
will be entirely yours.

And you have all my trust, I'm sure you can do it! :-D

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

      reply	other threads:[~2016-07-25 10:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <6E39C764-7DA4-4336-B366-8CAEB127066D@gmail.com>
2016-06-08 15:43 ` [Embedded-pv-devel] Xen Project Developer Summit : program Published Meng Xu
2016-07-15 12:01   ` Dario Faggioli
2016-07-15 14:56     ` Meng Xu
2016-07-25 10:50       ` 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=1469443820.13039.306.camel@citrix.com \
    --to=dario.faggioli@citrix.com \
    --cc=embedded-pv-devel@lists.xenproject.org \
    --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 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).