From: Peter Lieven <pl@dlh.net>
To: Vadim Rozenfeld <vrozenfe@redhat.com>
Cc: Gleb Natapov <gleb@redhat.com>,
qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] win7 bad i/o performance, high insn_emulation and exists
Date: Tue, 21 Feb 2012 19:21:15 +0100 [thread overview]
Message-ID: <4F43E09B.8050600@dlh.net> (raw)
In-Reply-To: <fdda386b-a781-4960-80d3-b898b32b9b76@zmail09.collab.prod.int.phx2.redhat.com>
On 21.02.2012 17:48, Vadim Rozenfeld wrote:
>
> ----- Original Message -----
> From: "Peter Lieven"<pl@dlh.net>
> To: "Vadim Rozenfeld"<vrozenfe@redhat.com>
> Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org, "Gleb Natapov"<gleb@redhat.com>
> Sent: Tuesday, February 21, 2012 4:10:22 PM
> Subject: Re: win7 bad i/o performance, high insn_emulation and exists
>
> On 21.02.2012 14:56, Vadim Rozenfeld wrote:
>> ----- Original Message -----
>> From: "Peter Lieven"<pl@dlh.net>
>> To: "Gleb Natapov"<gleb@redhat.com>
>> Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org, vrozenfe@redhat.com
>> Sent: Tuesday, February 21, 2012 2:05:25 PM
>> Subject: Re: win7 bad i/o performance, high insn_emulation and exists
>>
>> On 21.02.2012 12:46, Gleb Natapov wrote:
>>> On Tue, Feb 21, 2012 at 12:16:16PM +0100, Peter Lieven wrote:
>>>> 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.
>>>>
>> [VR]
>> Could it be that you have Driver Verifier running in you system?
>>
> unfortunately not.
>
> [VR]
> Then could you try booting into "Safe Mode"?
same picture.
next prev parent reply other threads:[~2012-02-21 18:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-20 18:17 [Qemu-devel] win7 bad i/o performance, high insn_emulation and exists Peter Lieven
2012-02-20 18:40 ` Gleb Natapov
2012-02-20 19:04 ` Gleb Natapov
2012-02-20 19:24 ` Peter Lieven
2012-02-20 19:59 ` Peter Lieven
2012-02-20 20:45 ` Gleb Natapov
2012-02-21 10:50 ` Peter Lieven
2012-02-21 10:56 ` Gleb Natapov
2012-02-21 10:59 ` Peter Lieven
2012-02-21 11:00 ` Gleb Natapov
2012-02-21 11:16 ` Peter Lieven
2012-02-21 11:46 ` Gleb Natapov
2012-02-21 12:05 ` Peter Lieven
2012-02-21 13:56 ` Vadim Rozenfeld
2012-02-21 14:10 ` Peter Lieven
2012-02-21 16:48 ` Vadim Rozenfeld
2012-02-21 18:21 ` Peter Lieven [this message]
2012-02-20 19:15 ` Peter Lieven
2012-02-20 20:42 ` 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=4F43E09B.8050600@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 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).