All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Marcelo Tosatti <marcelo-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org>
Cc: kvm-devel
	<kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
	virtualization-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: Re: [PATCH] kvm guest balloon driver
Date: Tue, 08 Jan 2008 18:18:13 +0200	[thread overview]
Message-ID: <4783A245.90002@qumranet.com> (raw)
In-Reply-To: <20080108161005.GA22168@dmt>

Marcelo Tosatti wrote:

 

>> Why is it taking over the irq?  This is very, very wrong.  A virtio 
>> device cannot be dependent on being used on top of the virtio-pci backend.
>>     
>
> A notification is necessary whenever the host changes the target value
> in the config space. So right now this notification is sharing the
> same IRQ as the main PCI device.
>
> Do you have any suggestion on how to retrieve the IRQ of the virtio
> device, or some other notification mechanism?
>   

One way would be to send a "look at config" queue message, but it seems 
that it is a fairly generic operation.  Maybe virtio can add support for 
it, with a new callback.

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


-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace

  parent reply	other threads:[~2008-01-08 16:18 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-08 15:33 [PATCH] kvm guest balloon driver Marcelo Tosatti
2008-01-08 15:42 ` Anthony Liguori
     [not found]   ` <478399D5.9030707-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
2008-01-08 16:10     ` Marcelo Tosatti
2008-01-08 16:14       ` [kvm-devel] " Anthony Liguori
2008-01-08 16:14       ` Anthony Liguori
     [not found]         ` <4783A14A.3080605-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
2008-01-08 16:36           ` Avi Kivity
     [not found]             ` <4783A68E.80901-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2008-01-08 16:43               ` Anthony Liguori
2008-01-08 16:43             ` [kvm-devel] " Anthony Liguori
2008-01-08 16:36         ` Avi Kivity
2008-01-08 16:18       ` Avi Kivity
2008-01-08 16:18       ` Avi Kivity [this message]
2008-01-09  3:20         ` Rusty Russell
     [not found]         ` <4783A245.90002-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2008-01-09  3:20           ` Rusty Russell
2008-01-09 10:06     ` Andrea Arcangeli
2008-01-09 11:14       ` [kvm-devel] " Marcelo Tosatti
     [not found]       ` <20080109100621.GL6958-lysg2Xt5kKMAvxtiuMwx3w@public.gmane.org>
2008-01-09 11:14         ` Marcelo Tosatti
2008-01-08 16:10   ` [kvm-devel] " Marcelo Tosatti
2008-01-09 10:06   ` Andrea Arcangeli
2008-01-08 15:42 ` Anthony Liguori
  -- strict thread matches above, loose matches on Subject: below --
2008-01-08 15:33 Marcelo Tosatti

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=4783A245.90002@qumranet.com \
    --to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=marcelo-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org \
    --cc=virtualization-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.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.