public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>, kvm@vger.kernel.org
Subject: Re: [PATCH v2 0/8] Move msix.o back to target independent files list
Date: Wed, 20 Oct 2010 12:38:02 +0200	[thread overview]
Message-ID: <4CBEC68A.4030904@redhat.com> (raw)
In-Reply-To: <20101020101833.GB12878@redhat.com>

  On 10/20/2010 12:18 PM, Michael S. Tsirkin wrote:
> On Sun, Oct 10, 2010 at 04:41:59PM +0200, Avi Kivity wrote:
> >  Due to a depedency on kvm's msix support, msix.c was changed to be a target
> >  dependent file.  This patch set changes it back.
> >
> >  v2: make the msix.c->kvm.c interface at a finer granularity, removing the need
> >      for kvm code to know about PCIDevice.
> >
> >  Avi Kivity (8):
> >    msix: avoid leaking kvm data on init failure
> >    kvm: drop kvm_context parameter from msix-related kvm functions
> >    Avoid using kvm_irq_routing_entry in PCIDevice
> >    Avoid use of kvm_irq_routing_entry in hw/msix.c
> >    kvm: Add stubs for msix support code
> >    kvm: allow kvm.h to be included from target independent files
> >    msix: remove CONFIG_KVM depedency
> >    Move msix.o build back to Makefile.objs
>
> Something strange happened: recent qemu-kvm seems much slower to me.
> Any chance kernel irqchip is now disabled?
>

You can use strace of ftrace to find out if the right ioctls or traces 
are called.

-- 
error compiling committee.c: too many arguments to function


      reply	other threads:[~2010-10-20 10:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-10 14:41 [PATCH v2 0/8] Move msix.o back to target independent files list Avi Kivity
2010-10-10 14:42 ` [PATCH v2 1/8] msix: avoid leaking kvm data on init failure Avi Kivity
2010-10-10 14:42 ` [PATCH v2 2/8] kvm: drop kvm_context parameter from msix-related kvm functions Avi Kivity
2010-10-10 14:42 ` [PATCH v2 3/8] Avoid using kvm_irq_routing_entry in PCIDevice Avi Kivity
2010-10-10 14:42 ` [PATCH v2 4/8] Avoid use of kvm_irq_routing_entry in hw/msix.c Avi Kivity
2010-10-10 14:42 ` [PATCH v2 5/8] kvm: Add stubs for msix support code Avi Kivity
2010-10-10 14:42 ` [PATCH v2 6/8] kvm: allow kvm.h to be included from target independent files Avi Kivity
2010-10-10 14:42 ` [PATCH v2 7/8] msix: remove CONFIG_KVM depedency Avi Kivity
2010-10-10 14:42 ` [PATCH v2 8/8] Move msix.o build back to Makefile.objs Avi Kivity
2010-10-10 15:02 ` [PATCH v2 0/8] Move msix.o back to target independent files list Michael S. Tsirkin
2010-10-20 10:18 ` Michael S. Tsirkin
2010-10-20 10:38   ` 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=4CBEC68A.4030904@redhat.com \
    --to=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=mtosatti@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