On Sat, Jul 4, 2020 at 10:45 AM Alex Bennée wrote:
>
>
> Aleksandar Markovic writes:
>
> > On Wednesday, July 1, 2020, Alex Bennée wrote:
> >
> >>
> >> Ahmed Karaman writes:
> >>
> >> > On Mon, Jun 29, 2020 at 6:03 PM Alex Bennée
> >> wrote:
> >> >>
> >> >> Assuming your test case is constant
On Saturday, July 4, 2020, Alex Bennée wrote:
>
> Aleksandar Markovic writes:
>
> > On Wednesday, July 1, 2020, Alex Bennée wrote:
> >
> >>
> >> Ahmed Karaman writes:
> >>
> >> > On Mon, Jun 29, 2020 at 6:03 PM Alex Bennée
> >> wrote:
> >> >>
> >> >> Assuming your test case is constant execut
On Saturday, July 4, 2020, Alex Bennée wrote:
>
> Aleksandar Markovic writes:
>
> > On Wednesday, July 1, 2020, Alex Bennée wrote:
> >
> >>
> >> Ahmed Karaman writes:
> >>
> >> > On Mon, Jun 29, 2020 at 6:03 PM Alex Bennée
> >> wrote:
> >> >>
> >> >> Assuming your test case is constant execut
Aleksandar Markovic writes:
> On Wednesday, July 1, 2020, Alex Bennée wrote:
>
>>
>> Ahmed Karaman writes:
>>
>> > On Mon, Jun 29, 2020 at 6:03 PM Alex Bennée
>> wrote:
>> >>
>> >> Assuming your test case is constant execution (i.e. runs the same each
>> >> time) you could run in through a p
On Wednesday, July 1, 2020, Alex Bennée wrote:
>
> Ahmed Karaman writes:
>
> > On Mon, Jun 29, 2020 at 6:03 PM Alex Bennée
> wrote:
> >>
> >> Assuming your test case is constant execution (i.e. runs the same each
> >> time) you could run in through a plugins build to extract the number of
> >>
On Wed, Jul 1, 2020 at 5:42 PM Alex Bennée wrote:
>
>
> Ahmed Karaman writes:
>
> > On Mon, Jun 29, 2020 at 6:03 PM Alex Bennée wrote:
> >>
> >> Assuming your test case is constant execution (i.e. runs the same each
> >> time) you could run in through a plugins build to extract the number of
> >
Ahmed Karaman writes:
> On Mon, Jun 29, 2020 at 6:03 PM Alex Bennée wrote:
>>
>> Assuming your test case is constant execution (i.e. runs the same each
>> time) you could run in through a plugins build to extract the number of
>> guest instructions, e.g.:
>>
>> ./aarch64-linux-user/qemu-aarc
On Mon, Jun 29, 2020 at 12:25 PM Ahmed Karaman
wrote:
>
> Hi,
>
> The second report of the TCG Continuous Benchmarking series builds
> upon the QEMU performance metrics calculated in the previous report.
> This report presents a method to dissect the number of instructions
> executed by a QEMU inv
On Mon, Jun 29, 2020 at 6:03 PM Alex Bennée wrote:
>
> Assuming your test case is constant execution (i.e. runs the same each
> time) you could run in through a plugins build to extract the number of
> guest instructions, e.g.:
>
> ./aarch64-linux-user/qemu-aarch64 -plugin tests/plugin/libinsn.s
On Tue, Jun 30, 2020 at 2:46 PM Lukáš Doktor wrote:
>
> > However, we know that the results for hosts of different architectures
> > will be different - we expect that.
> >
> > 32-bit Intel host will also most likely produce significantly
> > different results than 64-bit Intel hosts. By the way,
On Tue, Jun 30, 2020 at 11:52 AM Aleksandar Markovic
wrote:
>
> > As far as I know, this is how Ahmed test bed is setup:
> >
> > 1) Fresh installation on Ubuntu 18.04 on an Inter 64-bit host.
> > 2) Install QEMU build prerequisite packages.
> > 3) Install perf (this step is not necessary for Repor
Dne 30. 06. 20 v 11:41 Aleksandar Markovic napsal(a):
> уто, 30. јун 2020. у 06:34 Lukáš Doktor је написао/ла:
>>
>> Dne 29. 06. 20 v 12:25 Ahmed Karaman napsal(a):
>>> Hi,
>>>
>>> The second report of the TCG Continuous Benchmarking series builds
>>> upon the QEMU performance metrics calculated i
> However, we know that the results for hosts of different architectures
> will be different - we expect that.
>
> 32-bit Intel host will also most likely produce significantly
> different results than 64-bit Intel hosts. By the way, 64-bit targets
> in QEMU linux-user mode are not supported on 32
> As far as I know, this is how Ahmed test bed is setup:
>
> 1) Fresh installation on Ubuntu 18.04 on an Inter 64-bit host.
> 2) Install QEMU build prerequisite packages.
> 3) Install perf (this step is not necessary for Report 2, but it is
> for Report 1).
> 4) Install vallgrind.
> 5) Install 16 g
уто, 30. јун 2020. у 06:34 Lukáš Doktor је написао/ла:
>
> Dne 29. 06. 20 v 12:25 Ahmed Karaman napsal(a):
> > Hi,
> >
> > The second report of the TCG Continuous Benchmarking series builds
> > upon the QEMU performance metrics calculated in the previous report.
> > This report presents a method t
уто, 30. јун 2020. у 09:19 Ahmed Karaman
је написао/ла:
>
> On Tue, Jun 30, 2020 at 6:34 AM Lukáš Doktor wrote:
> >
> > Dne 29. 06. 20 v 12:25 Ahmed Karaman napsal(a):
> > > Hi,
> > >
> > > The second report of the TCG Continuous Benchmarking series builds
> > > upon the QEMU performance metrics
уто, 30. јун 2020. у 09:30 Ahmed Karaman
је написао/ла:
>
> On Tue, Jun 30, 2020 at 7:59 AM 罗勇刚(Yonggang Luo)
> wrote:
> >
> > Wonderful work, May I reproduce the work on my local machine?
> >
> > On Mon, Jun 29, 2020 at 6:26 PM Ahmed Karaman
> > wrote:
> >>
> >> Hi,
> >>
> >> The second repor
On Tue, Jun 30, 2020 at 7:59 AM 罗勇刚(Yonggang Luo) wrote:
>
> Wonderful work, May I reproduce the work on my local machine?
>
> On Mon, Jun 29, 2020 at 6:26 PM Ahmed Karaman
> wrote:
>>
>> Hi,
>>
>> The second report of the TCG Continuous Benchmarking series builds
>> upon the QEMU performance me
On Tue, Jun 30, 2020 at 6:34 AM Lukáš Doktor wrote:
>
> Dne 29. 06. 20 v 12:25 Ahmed Karaman napsal(a):
> > Hi,
> >
> > The second report of the TCG Continuous Benchmarking series builds
> > upon the QEMU performance metrics calculated in the previous report.
> > This report presents a method to d
Wonderful work, May I reproduce the work on my local machine?
On Mon, Jun 29, 2020 at 6:26 PM Ahmed Karaman
wrote:
> Hi,
>
> The second report of the TCG Continuous Benchmarking series builds
> upon the QEMU performance metrics calculated in the previous report.
> This report presents a method t
Dne 29. 06. 20 v 12:25 Ahmed Karaman napsal(a):
> Hi,
>
> The second report of the TCG Continuous Benchmarking series builds
> upon the QEMU performance metrics calculated in the previous report.
> This report presents a method to dissect the number of instructions
> executed by a QEMU invocation
On Mon, Jun 29, 2020 at 6:03 PM Alex Bennée wrote:
>
>
> Ahmed Karaman writes:
>
> > Hi,
> >
> > The second report of the TCG Continuous Benchmarking series builds
> > upon the QEMU performance metrics calculated in the previous report.
> > This report presents a method to dissect the number of i
> I should have also pointed out in your
> by only having one benchmark you are going to miss out on the envelope
> of use cases.
>
Alex, thank you for all your comments, and other perspectives that you
always bring to Ahmed's and everyones else's attention. I always imagine
you as a "four-dimensi
Ahmed Karaman writes:
> Hi,
>
> The second report of the TCG Continuous Benchmarking series builds
> upon the QEMU performance metrics calculated in the previous report.
> This report presents a method to dissect the number of instructions
> executed by a QEMU invocation into three main phases:
Thank you for your support!
On Mon, Jun 29, 2020, 12:40 PM Aleksandar Markovic <
aleksandar.qemu.de...@gmail.com> wrote:
>
>
> понедељак, 29. јун 2020., Ahmed Karaman је
> написао/ла:
>
>> Hi,
>>
>> The second report of the TCG Continuous Benchmarking series builds
>> upon the QEMU performance m
понедељак, 29. јун 2020., Ahmed Karaman је
написао/ла:
> Hi,
>
> The second report of the TCG Continuous Benchmarking series builds
> upon the QEMU performance metrics calculated in the previous report.
> This report presents a method to dissect the number of instructions
> executed by a QEMU inv
Hi,
The second report of the TCG Continuous Benchmarking series builds
upon the QEMU performance metrics calculated in the previous report.
This report presents a method to dissect the number of instructions
executed by a QEMU invocation into three main phases:
- Code Generation
- JIT Execution
-
27 matches
Mail list logo
