All of lore.kernel.org
 help / color / mirror / Atom feed
From: sheng qiu <herbert1984106@gmail.com>
To: Avi Kivity <avi@redhat.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: Thu, 12 Jul 2012 12:32:21 -0500	[thread overview]
Message-ID: <CAB7xdinaGFxyn3OHmsq0Lqtkfs9XST0j0Tj4kBvQGNf5UxWLvw@mail.gmail.com> (raw)
In-Reply-To: <4FFE8FEB.2020606@redhat.com>

thanks for your reply.
the value is very large. 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?

Thanks,
Sheng

On Thu, Jul 12, 2012 at 3:50 AM, Avi Kivity <avi@redhat.com> wrote:
> On 07/12/2012 02:54 AM, sheng qiu wrote:
>> Hi all,
>>
>> i saw lots of APIC_TMICT exits while running a linux guest with
>> assigned NIC. The APIC_TMICT exits is only a little fewer than the
>> number of injected interrupts while handling network traffic on the
>> assigned NIC.
>> The network traffic was generated by running netperf on another
>> machine targeted at the VM.
>>
>> Is this normal? if not, what kind of problem may cause it?
>
> I'm guessing the driver sets a timer on every interrupt.
>
> What is the value written?  If it's large, perhaps we can set some slack
> on the timer so it's not re-set every time.
>
>
> --
> error compiling committee.c: too many arguments to function
>
>



-- 
Sheng Qiu
Texas A & M University
Room 332B Wisenbaker
email: herbert1984106@gmail.com
College Station, TX 77843-3259

  reply	other threads:[~2012-07-12 17:32 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 [this message]
2012-07-15  8:03     ` Avi Kivity

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=CAB7xdinaGFxyn3OHmsq0Lqtkfs9XST0j0Tj4kBvQGNf5UxWLvw@mail.gmail.com \
    --to=herbert1984106@gmail.com \
    --cc=avi@redhat.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.