From: Jan Kiszka <jan.kiszka@siemens.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: kvm <kvm@vger.kernel.org>
Subject: Re: Suggestions for testing VAPIC / TPR patching
Date: Thu, 19 Jan 2012 10:14:53 +0100 [thread overview]
Message-ID: <4F17DF0D.7020308@siemens.com> (raw)
In-Reply-To: <20120119090219.GG9571@redhat.com>
On 2012-01-19 10:02, Gleb Natapov wrote:
> On Thu, Jan 19, 2012 at 09:35:47AM +0100, Jan Kiszka wrote:
>> Hi again,
>>
>> what is the best way to check if the TPR patching feature of qemu-kvm is
>> working and performs efficiently? I suppose Windows XP guests, e.g.? How
>> to measure this best? I'm about to start porting it to upstream and like
>> to prepare a good test case.
>>
> Run WindowsXP on AMD HW without vapic and see number of TPR access exits.
> Than run it with vapic and check again. Don't forget to check that
> reboot et al work.
So is this an optimization only for AMD CPUs or can it be reproduced on
Intel as well? Any CPU feature dependencies?
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2012-01-19 9:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-19 8:35 Suggestions for testing VAPIC / TPR patching Jan Kiszka
2012-01-19 9:02 ` Gleb Natapov
2012-01-19 9:14 ` Jan Kiszka [this message]
2012-01-19 9:27 ` 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=4F17DF0D.7020308@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=gleb@redhat.com \
--cc=kvm@vger.kernel.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.