qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Orit Wasserman <owasserm@redhat.com>
To: "\"陳韋任 (Wei-Ren Chen)\"" <chenwj@iis.sinica.edu.tw>
Subject: Re: [Qemu-devel] How to measure guest memory access (qemu_ld/qemu_st) time?
Date: Tue, 19 Jun 2012 12:01:08 +0300	[thread overview]
Message-ID: <4FE03FD4.4070508@redhat.com> (raw)
In-Reply-To: <20120619084939.GA37515@cs.nctu.edu.tw>

On 06/19/2012 11:49 AM, 陳韋任 (Wei-Ren Chen) wrote:
>   Mind me CC this to ML? :)
sure I will read the threads to understand more.

Orit
> 
>> Well it was a while back (2008-9) ,the company was acquired by IBM a year later :
>> http://www.linux-kvm.org/wiki/images/9/98/KvmForum2008%24kdf2008_2.pdf
>> I think stefan Hanjoczi worked there ...
>> The company used the technology for cross platform guest support but claim to get speedup too
>> (for ppc) don't think the speedup was related to mmu but more to the instruction stream.
>> I hope this is helpful.
> 
>   Thanks.
>  
>> Do you have performance result for the cost of the address translation ?
>> If I understand you are concentrating on ARM ?
> 
>   The whole discussion thread is on [1], and you can get some feel about
> the cost of address translation here [2]. Yes, ARM is our target right now,
> but I think we are not limit to it. 
> 
> Regards,
> chenwj
> 
> [1] http://www.mail-archive.com/qemu-devel@nongnu.org/msg116159.html
> [2] http://www.mail-archive.com/qemu-devel@nongnu.org/msg116404.html
> 

  parent reply	other threads:[~2012-06-19  9:03 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-13  3:14 [Qemu-devel] How to measure guest memory access (qemu_ld/qemu_st) time? 陳韋任 (Wei-Ren Chen)
2012-06-13  9:18 ` Stefan Hajnoczi
2012-06-13 12:43   ` Lluís Vilanova
2012-06-14  3:29     ` 陳韋任 (Wei-Ren Chen)
2012-06-14 23:17       ` Lluís Vilanova
2012-06-13 10:43 ` Laurent Desnogues
2012-06-14  3:18   ` 陳韋任 (Wei-Ren Chen)
2012-06-14 22:30     ` Lluís Vilanova
2012-06-15  8:23       ` Laurent Desnogues
2012-06-15 19:10         ` Lluís Vilanova
2012-06-18  8:28     ` 陳韋任 (Wei-Ren Chen)
2012-06-18 19:36       ` Blue Swirl
2012-06-18 20:26         ` Lluís Vilanova
2012-06-19  7:52           ` 陳韋任 (Wei-Ren Chen)
2012-06-19  9:35             ` Michael.Kang
2012-06-19  9:47           ` Michael.Kang
2012-06-19 10:51             ` Lluís Vilanova
2012-06-18 19:38       ` Lluís Vilanova
     [not found]       ` <20120619075534.GB34488@cs.nctu.edu.tw>
     [not found]         ` <4FE0347A.9040309@redhat.com>
     [not found]           ` <20120619084939.GA37515@cs.nctu.edu.tw>
2012-06-19  9:01             ` Orit Wasserman [this message]
2012-06-14  3:31   ` 陳韋任 (Wei-Ren Chen)
  -- strict thread matches above, loose matches on Subject: below --
2012-06-14 12:35 YeongKyoon Lee
2012-06-15 19:20 ` Blue Swirl
2012-06-18  6:57   ` 陳韋任 (Wei-Ren Chen)
2012-06-18 19:28     ` Blue Swirl
2012-06-15  2:10 YeongKyoon Lee
2012-06-18  4:59 YeongKyoon Lee
2012-06-18 19:21 ` Blue Swirl
2012-06-20  7:57 陳韋任 (Wei-Ren Chen)
2012-06-22  9:58 ` Xin Tong
2012-06-24  6:13   ` Blue Swirl

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=4FE03FD4.4070508@redhat.com \
    --to=owasserm@redhat.com \
    --cc=chenwj@iis.sinica.edu.tw \
    /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).