From: Avi Kivity <avi@redhat.com>
To: sheng qiu <herbert1984106@gmail.com>
Cc: kvm <kvm@vger.kernel.org>, linux-kernel@vger.kernel.org
Subject: Re: lots of APIC_TMICT exit on VM with assigned NIC
Date: Sun, 15 Jul 2012 11:03:03 +0300 [thread overview]
Message-ID: <50027937.60803@redhat.com> (raw)
In-Reply-To: <CAB7xdinaGFxyn3OHmsq0Lqtkfs9XST0j0Tj4kBvQGNf5UxWLvw@mail.gmail.com>
On 07/12/2012 08:32 PM, sheng qiu wrote:
> thanks for your reply.
> the value is very large.
Can you provide samples?
If it's large and fairly constant it means a timer keeps being pushed
back by the interrupts/
> is there anyway that i can avoid such
> frequent exits due to APIC_TMICT? do i need to modify some codes in
> kvm kernel module or adapt some parameters?
>
No, a guest change is needed. You need to find out what timer is
involved at modify it to set some slack, with
hrtimer_set_expires_range() or similar.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2012-07-15 8:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-11 23:54 lots of APIC_TMICT exit on VM with assigned NIC sheng qiu
2012-07-12 8:50 ` Avi Kivity
2012-07-12 17:32 ` sheng qiu
2012-07-15 8:03 ` Avi Kivity [this message]
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=50027937.60803@redhat.com \
--to=avi@redhat.com \
--cc=herbert1984106@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@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.