qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Jes Sorensen <Jes.Sorensen@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: [PATCH 1/7] Only call kvm_set_irqfd() if CONFIG_KVM is defined
Date: Tue, 15 Jun 2010 15:48:50 +0200	[thread overview]
Message-ID: <4C1784C2.2040604@redhat.com> (raw)
In-Reply-To: <4C1782CE.5050105@redhat.com>

On 06/15/2010 03:40 PM, Jes Sorensen wrote:
> On 06/15/10 15:31, Paolo Bonzini wrote:
>> On 06/15/2010 01:04 PM, Jes.Sorensen@redhat.com wrote:
>>> From: Jes Sorensen<Jes.Sorensen@redhat.com>
>>>
>>> Only call kvm_set_irqfd() if CONFIG_KVM is defined to avoid breaking
>>> the build for non x86.
>>
>> You can just add a stub to kvm-stub.c that returns -ENOSYS.
>>
>> Paolo
>
> It's more than that, the code also uses bits in the msix code that isn't
> globally available.

I see now.  BTW, my eventnotifier series conflicts with this part of 
qemu-kvm, so it's probably better if I work that series out in qemu-kvm 
first and then upstream.  As I would touch this code anyway, I think 
your patch is fine even if it were be only a stopgap measure.

Maybe the right fix, which I could include in my series, is to change 
kvm_set_irqfd's calling convention to be like this:

     int r = kvm_set_irqfd(&dev->msix_irq_entries[vector],
                           event_notifier_get_fd(notifier),
                           !masked);

and extract the gsi in the function.  Michael, does this make any sense?

Paolo

  reply	other threads:[~2010-06-15 13:49 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-15 11:04 [Qemu-devel] [PATCH 0/7] Fix building qemu-kvm for non KVM target Jes.Sorensen
2010-06-15 11:04 ` [Qemu-devel] [PATCH 1/7] Only call kvm_set_irqfd() if CONFIG_KVM is defined Jes.Sorensen
2010-06-15 13:31   ` [Qemu-devel] " Paolo Bonzini
2010-06-15 13:40     ` Jes Sorensen
2010-06-15 13:48       ` Paolo Bonzini [this message]
2010-06-15 14:58         ` Michael S. Tsirkin
2010-06-15 11:04 ` [Qemu-devel] [PATCH 2/7] No need for kvm_init() stub as already defined in qemu-kvm.h Jes.Sorensen
2010-06-15 13:34   ` [Qemu-devel] " Paolo Bonzini
2010-06-15 13:59     ` Jes Sorensen
2010-06-15 11:04 ` [Qemu-devel] [PATCH 3/7] time_drift_fix is x86 only, rather than !ia64 Jes.Sorensen
2010-06-15 11:04 ` [Qemu-devel] [PATCH 4/7] Build certain drivers for MIPS as well Jes.Sorensen
2010-06-15 11:04 ` [Qemu-devel] [PATCH 5/7] Only export phys_mem create functions for !CONFIG_USER_ONLY builds Jes.Sorensen
2010-06-15 13:35   ` [Qemu-devel] " Paolo Bonzini
2010-06-15 11:04 ` [Qemu-devel] [PATCH 6/7] Only treat KVM specific cmdline options for KVM enabled builds Jes.Sorensen
2010-06-15 11:04 ` [Qemu-devel] [PATCH 7/7] Only accept -no-hpet for i386 targets Jes.Sorensen
2010-06-15 12:20   ` [Qemu-devel] " Jan Kiszka
2010-06-15 12:28     ` Jes Sorensen
2010-06-15 12:37       ` Jan Kiszka
2010-06-15 12:44         ` Jes Sorensen
2010-06-15 13:38   ` Paolo Bonzini
2010-06-15 13:42     ` Jes Sorensen
2010-06-15 12:04 ` [Qemu-devel] Re: [PATCH 0/7] Fix building qemu-kvm for non KVM target Avi Kivity
2010-06-15 12:06   ` Avi Kivity
2010-06-15 12:10   ` Jes Sorensen
2010-06-15 13:42     ` Juan Quintela
2010-06-15 13:44       ` Jes Sorensen

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=4C1784C2.2040604@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=Jes.Sorensen@redhat.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.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 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).