From: Christoffer Dall <christoffer.dall@linaro.org>
To: Andre Przywara <andre.przywara@linaro.org>
Cc: Marc Zyngier <marc.zyngier@arm.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
Stefano Stabellini <sstabellini@kernel.org>,
Julien Grall <julien.grall@linaro.org>,
Eric Auger <eric.auger@redhat.com>
Subject: Re: [RFC] ARM: New (Xen) VGIC design document
Date: Thu, 2 Nov 2017 08:38:33 +0100 [thread overview]
Message-ID: <CAMJs5B9uY6+9iszQEOOBErZfDddi5OquPh2s1+kmPL+vpfTcxw@mail.gmail.com> (raw)
In-Reply-To: <37740904-434c-7372-91ac-adc5acf5eb8c@linaro.org>
On Wed, Nov 1, 2017 at 10:15 AM, Andre Przywara
<andre.przywara@linaro.org> wrote:
> Hi,
>
> On 01/11/17 04:31, Christoffer Dall wrote:
>> On Wed, Nov 1, 2017 at 9:58 AM, Stefano Stabellini
>> <sstabellini@kernel.org> wrote:
>>
>> [....]
>
> Christoffer, many thanks for answering this!
> I think we have a lot of assumptions about the whole VGIC life cycle
> floating around, but it would indeed be good to get some numbers behind it.
> I would be all too happy to trace some workloads on Xen again and
> getting some metrics, though this sounds time consuming if done properly.
>
> Do you have any numbers on VGIC performance available somewhere?
>
I ran the full set of workloads and micro numbers that I've used for
my papers with/without the optimization, and couldn't find a
measurable difference.
-Christoffer
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-11-02 7:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-11 14:33 [RFC] ARM: New (Xen) VGIC design document Andre Przywara
2017-10-11 14:42 ` Andre Przywara
2017-10-12 12:05 ` Christoffer Dall
2017-11-01 17:54 ` Andre Przywara
2017-11-01 1:58 ` Stefano Stabellini
2017-11-01 4:31 ` Christoffer Dall
2017-11-01 9:15 ` Andre Przywara
2017-11-02 7:38 ` Christoffer Dall [this message]
2017-11-01 14:30 ` Andre Przywara
2017-11-01 21:54 ` Stefano Stabellini
2017-11-02 7:40 ` Christoffer Dall
2017-11-02 16:00 ` Andre Przywara
2017-11-02 17:56 ` Stefano Stabellini
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=CAMJs5B9uY6+9iszQEOOBErZfDddi5OquPh2s1+kmPL+vpfTcxw@mail.gmail.com \
--to=christoffer.dall@linaro.org \
--cc=andre.przywara@linaro.org \
--cc=eric.auger@redhat.com \
--cc=julien.grall@linaro.org \
--cc=marc.zyngier@arm.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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.