From: Stefano Stabellini <sstabellini@kernel.org>
To: Julien Grall <julien.grall@arm.com>
Cc: nd@arm.com, Stefano Stabellini <sstabellini@kernel.org>,
andrii_anisov@epam.com,
Stefano Stabellini <stefano.stabellini@xilinx.com>,
Milan Boberic <milanboberic94@gmail.com>,
Dario Faggioli <dfaggioli@suse.com>,
Julien Grall <julien.grall@gmail.com>,
Meng Xu <xumengpanda@gmail.com>,
xen-devel@lists.xenproject.org,
Andrii Anisov <andrii.anisov@gmail.com>
Subject: Re: Xen optimization
Date: Tue, 11 Dec 2018 10:39:01 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.10.1812111038130.12259@sstabellini-ThinkPad-X260> (raw)
In-Reply-To: <1ca5735f-638a-6949-6a15-2fe4aa665114@arm.com>
On Tue, 11 Dec 2018, Julien Grall wrote:
> On 10/12/2018 12:23, Andrii Anisov wrote:
> > Hello Julien,
> >
> > On 10.12.18 13:54, Julien Grall wrote:
> > > What are the numbers without Xen?
> > Good question. Didn't try. At least putchar should be implemented for that.
>
> I think we need the baremetal numbers to be able to compare properly the old
> and new vGIC.
That might prove very hard for Andrii to do because TBM is made to run
on Xilinx hardware and Xen VMs only. It is probably lacking necessary
drivers to run on other boards natively.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-12-11 18:39 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-09 10:59 Xen optimization Milan Boberic
2018-10-09 16:46 ` Dario Faggioli
2018-10-10 11:22 ` Milan Boberic
2018-10-10 11:25 ` Milan Boberic
2018-10-10 16:41 ` Meng Xu
2018-10-11 7:36 ` Milan Boberic
2018-10-11 12:17 ` Milan Boberic
2018-10-11 17:05 ` Dario Faggioli
2018-10-11 15:39 ` Meng Xu
2018-10-11 22:29 ` Stefano Stabellini
2018-10-12 15:33 ` Milan Boberic
2018-10-12 16:36 ` Julien Grall
2018-10-12 17:43 ` Stefano Stabellini
2018-10-13 16:01 ` Milan Boberic
2018-10-14 22:46 ` Stefano Stabellini
2018-10-15 12:27 ` Milan Boberic
2018-10-16 7:13 ` Stefano Stabellini
2018-10-15 8:14 ` Julien Grall
2018-10-15 12:50 ` Julien Grall
2018-10-15 13:01 ` Milan Boberic
2018-10-15 13:03 ` Julien Grall
2018-10-17 15:19 ` Milan Boberic
2018-10-19 21:02 ` Stefano Stabellini
2018-10-19 22:41 ` Dario Faggioli
2018-10-22 15:02 ` Milan Boberic
2018-10-22 17:52 ` Stefano Stabellini
2018-10-23 8:58 ` Milan Boberic
2018-10-24 0:24 ` Stefano Stabellini
2018-10-25 10:09 ` Milan Boberic
2018-10-25 11:30 ` Julien Grall
2018-10-25 12:36 ` Milan Boberic
2018-10-25 13:44 ` Dario Faggioli
2018-10-25 14:00 ` Julien Grall
2018-10-25 14:04 ` Julien Grall
2018-10-25 14:47 ` Milan Boberic
2018-10-25 14:51 ` Julien Grall
2018-10-25 16:18 ` Xen optimizationcy Stefano Stabellini
2018-10-25 11:09 ` Xen optimization Julien Grall
2018-10-25 16:15 ` Stefano Stabellini
2018-10-26 19:12 ` Julien Grall
2018-10-26 20:41 ` Stefano Stabellini
2018-10-29 12:29 ` Milan Boberic
2018-10-31 18:59 ` Julien Grall
2018-10-31 20:35 ` Milan Boberic
2018-10-31 21:16 ` Julien Grall
2018-11-01 20:20 ` Stefano Stabellini
2018-11-01 20:35 ` Julien Grall
2018-11-20 11:33 ` Andrii Anisov
2018-11-27 21:27 ` Stefano Stabellini
2018-11-29 8:19 ` Andrii Anisov
2018-12-10 10:58 ` Andrii Anisov
2018-12-10 11:54 ` Julien Grall
2018-12-10 12:23 ` Andrii Anisov
2018-12-11 12:27 ` Julien Grall
2018-12-11 16:56 ` Dario Faggioli
2018-12-12 9:39 ` Andrii Anisov
2018-12-12 17:10 ` Dario Faggioli
2018-12-12 17:32 ` Andrii Anisov
2018-12-12 17:59 ` Dario Faggioli
2018-12-13 7:48 ` Andrii Anisov
2018-12-11 18:39 ` Stefano Stabellini [this message]
2018-12-11 19:05 ` Julien Grall
2018-12-11 19:29 ` Stefano Stabellini
2018-12-12 9:46 ` Andrii Anisov
2018-12-12 10:41 ` Andrii Anisov
2018-12-12 17:39 ` Stefano Stabellini
2018-12-12 17:47 ` Andrii Anisov
2018-12-12 18:01 ` Stefano Stabellini
2018-12-12 9:34 ` Andrii Anisov
2018-11-07 13:14 ` 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=alpine.DEB.2.10.1812111038130.12259@sstabellini-ThinkPad-X260 \
--to=sstabellini@kernel.org \
--cc=andrii.anisov@gmail.com \
--cc=andrii_anisov@epam.com \
--cc=dfaggioli@suse.com \
--cc=julien.grall@arm.com \
--cc=julien.grall@gmail.com \
--cc=milanboberic94@gmail.com \
--cc=nd@arm.com \
--cc=stefano.stabellini@xilinx.com \
--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 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.