From: Peng Fan <van.freenix@gmail.com>
To: Julien Grall <julien.grall@arm.com>
Cc: Dario Faggioli <dario.faggioli@citrix.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Anastassios Nanos <anastassios.nanos@gmail.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Big.LITTLE support (WAS Re: Xen ARM community call)
Date: Thu, 24 Nov 2016 15:40:27 +0800 [thread overview]
Message-ID: <20161124074000.GA18264@linux-u7w5.ap.freescale.net> (raw)
In-Reply-To: <cff18dc7-a968-af2d-0848-3678c0fbfb0b@arm.com>
Hi Julien,
On Tue, Nov 22, 2016 at 02:28:39PM +0000, Julien Grall wrote:
>Hello Anastassios,
>
>On 09/11/16 22:50, Anastassios Nanos wrote:
>>Hi Julien, all,
>>
>>>I would like to start organizing a recurring community call to discuss and
>>>sync-up on upcoming features for Xen ARM.
>>
>>great idea, I'd like to join too (GMT).
>>
>>>Example of features that could be discussed:
>>> - Sharing co-processor between guests
>>> - PCI passthrough
>>
>>Another issue to discuss, at some point, could be big.LITTLE support
>>(based on https://lists.xenproject.org/archives/html/xen-devel/2016-09/msg01802.html).
>
>Good point. Looking at the discussion, many ideas was suggested and I don't
>remember whether we all agreed on what to do. I would recommend to summarize
>the discussion in a mail so we can come up with an agreement.
>
>Peng, would you be up to do this?
Sorry for late reply. I am a bit busy on other things. I appreciate if you or anyone else
can help summarize the ideas. I may come to this big.little stuff at the beginning
of Dec.
Thanks,
Peng.
>
>Regards,
>
>--
>Julien Grall
>
>_______________________________________________
>Xen-devel mailing list
>Xen-devel@lists.xen.org
>https://lists.xen.org/xen-devel
--
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-11-24 7:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-08 12:19 Xen ARM community call Julien Grall
2016-11-08 13:04 ` Andrii Anisov
2016-11-08 13:31 ` Edgar E. Iglesias
2016-11-08 13:51 ` Meng Xu
2016-11-08 16:17 ` Stewart Hildebrand
2016-11-08 16:50 ` Iurii Mykhalskyi
2016-11-08 16:56 ` Chris Patterson
2016-11-08 17:07 ` Ruigrok, Richard
2016-11-08 17:06 ` Alistair Francis
2016-11-08 17:26 ` Edward Sandberg
2016-11-08 18:19 ` Stefano Stabellini
2016-11-09 7:32 ` Dirk Behme
2016-11-22 14:19 ` Julien Grall
2016-11-09 22:50 ` Anastassios Nanos
2016-11-22 14:28 ` Big.LITTLE support (WAS Re: Xen ARM community call) Julien Grall
2016-11-22 17:52 ` Dario Faggioli
2016-11-24 7:40 ` Peng Fan [this message]
2016-11-24 9:48 ` Dario Faggioli
2016-11-16 20:34 ` Xen ARM community call Goel, Sameer
2016-11-18 16:07 ` Julien Grall
2016-11-22 13:48 ` Julien Grall
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=20161124074000.GA18264@linux-u7w5.ap.freescale.net \
--to=van.freenix@gmail.com \
--cc=anastassios.nanos@gmail.com \
--cc=dario.faggioli@citrix.com \
--cc=julien.grall@arm.com \
--cc=sstabellini@kernel.org \
--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.