All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Lieven <pl@dlh.net>
To: Gleb Natapov <gleb@redhat.com>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org, vrozenfe@redhat.com
Subject: Re: win7 bad i/o performance, high insn_emulation and exists
Date: Tue, 21 Feb 2012 12:16:16 +0100	[thread overview]
Message-ID: <4F437D00.8050102@dlh.net> (raw)
In-Reply-To: <20120221110057.GA27471@redhat.com>

On 21.02.2012 12:00, Gleb Natapov wrote:
> On Tue, Feb 21, 2012 at 11:59:23AM +0100, Peter Lieven wrote:
>> On 21.02.2012 11:56, Gleb Natapov wrote:
>>> On Tue, Feb 21, 2012 at 11:50:47AM +0100, Peter Lieven wrote:
>>>>> I hope it will make Windows use TSC instead, but you can't be sure
>>>>> about anything with Windows :(
>>>> Whatever it does now it eates more CPU has almost equal
>>>> number of exits and throughput is about the same (15MB/s).
>>>> If pmtimer is at 0xb008 it still reads it like hell.
>>>>
>>>> I checked with bcedit /v that useplatformclock is set to "No".
>>> Yeah, today I noticed that it is likely virtio drivers that hammer
>>> on PM timer (at least rip of the instruction that access it is
>>> very close to rip of the instruction that access virtio pio).
>>> Vadim, Windows driver developer,  is CCed.
>> Ok, I will switch to IDE and e1000 to confirm this? Or does it not
>> make sense?
>>
> It make perfect sense! Please try it.
~10MB/s. still a lot of 0xb008 reads.

efer_reload                    0         0
exits                    4389875     72341
fpu_reload                 36729       342
halt_exits                206204      3451
halt_wakeup               212953      3474
host_state_reload        2976799     59043
hypercalls                     0         0
insn_emulation           2936091     54921
insn_emulation_fail            0         0
invlpg                         0         0
io_exits                 1821386     14108
irq_exits                  81999      2798
irq_injections            343720      8560
irq_window                 12712       153
largepages                   754         2
mmio_exits                    37         0
mmu_cache_miss               148         0
mmu_flooded                    0         0
mmu_pde_zapped                 0         0
mmu_pte_updated                0         0
mmu_pte_write                  0         0
mmu_recycled                   0         0
mmu_shadow_zapped            189         0
mmu_unsync                     0         0
nmi_injections                 0         0
nmi_window                     0         0
pf_fixed                  139461        21
pf_guest                       0         0
remote_tlb_flush             248         0
request_irq                    0         0
signal_exits                   0         0
tlb_flush                  15366         0

trace at http://82.141.21.156/report3.txt.gz

Peter
> --
> 			Gleb.


WARNING: multiple messages have this Message-ID (diff)
From: Peter Lieven <pl@dlh.net>
To: Gleb Natapov <gleb@redhat.com>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org, vrozenfe@redhat.com
Subject: Re: [Qemu-devel] win7 bad i/o performance, high insn_emulation and exists
Date: Tue, 21 Feb 2012 12:16:16 +0100	[thread overview]
Message-ID: <4F437D00.8050102@dlh.net> (raw)
In-Reply-To: <20120221110057.GA27471@redhat.com>

On 21.02.2012 12:00, Gleb Natapov wrote:
> On Tue, Feb 21, 2012 at 11:59:23AM +0100, Peter Lieven wrote:
>> On 21.02.2012 11:56, Gleb Natapov wrote:
>>> On Tue, Feb 21, 2012 at 11:50:47AM +0100, Peter Lieven wrote:
>>>>> I hope it will make Windows use TSC instead, but you can't be sure
>>>>> about anything with Windows :(
>>>> Whatever it does now it eates more CPU has almost equal
>>>> number of exits and throughput is about the same (15MB/s).
>>>> If pmtimer is at 0xb008 it still reads it like hell.
>>>>
>>>> I checked with bcedit /v that useplatformclock is set to "No".
>>> Yeah, today I noticed that it is likely virtio drivers that hammer
>>> on PM timer (at least rip of the instruction that access it is
>>> very close to rip of the instruction that access virtio pio).
>>> Vadim, Windows driver developer,  is CCed.
>> Ok, I will switch to IDE and e1000 to confirm this? Or does it not
>> make sense?
>>
> It make perfect sense! Please try it.
~10MB/s. still a lot of 0xb008 reads.

efer_reload                    0         0
exits                    4389875     72341
fpu_reload                 36729       342
halt_exits                206204      3451
halt_wakeup               212953      3474
host_state_reload        2976799     59043
hypercalls                     0         0
insn_emulation           2936091     54921
insn_emulation_fail            0         0
invlpg                         0         0
io_exits                 1821386     14108
irq_exits                  81999      2798
irq_injections            343720      8560
irq_window                 12712       153
largepages                   754         2
mmio_exits                    37         0
mmu_cache_miss               148         0
mmu_flooded                    0         0
mmu_pde_zapped                 0         0
mmu_pte_updated                0         0
mmu_pte_write                  0         0
mmu_recycled                   0         0
mmu_shadow_zapped            189         0
mmu_unsync                     0         0
nmi_injections                 0         0
nmi_window                     0         0
pf_fixed                  139461        21
pf_guest                       0         0
remote_tlb_flush             248         0
request_irq                    0         0
signal_exits                   0         0
tlb_flush                  15366         0

trace at http://82.141.21.156/report3.txt.gz

Peter
> --
> 			Gleb.

  reply	other threads:[~2012-02-21 11:16 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-20 18:17 win7 bad i/o performance, high insn_emulation and exists Peter Lieven
2012-02-20 18:17 ` [Qemu-devel] " Peter Lieven
2012-02-20 18:40 ` Gleb Natapov
2012-02-20 18:40   ` [Qemu-devel] " Gleb Natapov
2012-02-20 19:04   ` Gleb Natapov
2012-02-20 19:04     ` [Qemu-devel] " Gleb Natapov
2012-02-20 19:24     ` Peter Lieven
2012-02-20 19:24       ` [Qemu-devel] " Peter Lieven
2012-02-20 19:59     ` Peter Lieven
2012-02-20 19:59       ` [Qemu-devel] " Peter Lieven
2012-02-20 20:45       ` Gleb Natapov
2012-02-20 20:45         ` [Qemu-devel] " Gleb Natapov
2012-02-21 10:50         ` Peter Lieven
2012-02-21 10:50           ` [Qemu-devel] " Peter Lieven
2012-02-21 10:56           ` Gleb Natapov
2012-02-21 10:56             ` [Qemu-devel] " Gleb Natapov
2012-02-21 10:59             ` Peter Lieven
2012-02-21 10:59               ` [Qemu-devel] " Peter Lieven
2012-02-21 11:00               ` Gleb Natapov
2012-02-21 11:00                 ` [Qemu-devel] " Gleb Natapov
2012-02-21 11:16                 ` Peter Lieven [this message]
2012-02-21 11:16                   ` Peter Lieven
2012-02-21 11:46                   ` Gleb Natapov
2012-02-21 11:46                     ` [Qemu-devel] " Gleb Natapov
2012-02-21 12:05                     ` Peter Lieven
2012-02-21 12:05                       ` [Qemu-devel] " Peter Lieven
2012-02-21 13:56                       ` Vadim Rozenfeld
2012-02-21 13:56                         ` [Qemu-devel] " Vadim Rozenfeld
2012-02-21 14:10                         ` Peter Lieven
2012-02-21 14:10                           ` [Qemu-devel] " Peter Lieven
2012-02-21 16:48                           ` Vadim Rozenfeld
2012-02-21 16:48                             ` [Qemu-devel] " Vadim Rozenfeld
2012-02-21 18:21                             ` Peter Lieven
2012-02-21 18:21                               ` [Qemu-devel] " Peter Lieven
2012-02-20 19:15   ` Peter Lieven
2012-02-20 19:15     ` [Qemu-devel] " Peter Lieven
2012-02-20 20:42     ` Gleb Natapov
2012-02-20 20:42       ` [Qemu-devel] " Gleb Natapov

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=4F437D00.8050102@dlh.net \
    --to=pl@dlh.net \
    --cc=gleb@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.org \
    --cc=vrozenfe@redhat.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.