public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Christian Borntraeger <borntraeger@de.ibm.com>,
	Rusty Russell <rusty@rustcorp.com.au>,
	virtualization@lists.linux-foundation.org, kvm@vger.kernel.org,
	avi@redhat.com, Carsten Otte <cotte@de.ibm.com>
Subject: Re: [PATCH RFC 0/2] qemu-kvm: MSI-X support
Date: Tue, 12 May 2009 16:45:21 +0300	[thread overview]
Message-ID: <20090512134521.GC23796@redhat.com> (raw)
In-Reply-To: <4A08A599.1070708@codemonkey.ws>

On Mon, May 11, 2009 at 05:24:25PM -0500, Anthony Liguori wrote:
> Michael S. Tsirkin wrote:
>> Here's a draft MSI-X support patch. Among missing features:
>> save/load support, and command-line flag to control the
>> feature. This is on top of qemu-kvm: msi-x is disabled
>> without kvm interrupt injection support for now.
>>   
>
> What's your impression of how much work would be to get this going on  
> top of upstream QEMU?
>
> I'm willing to borrow a few cycles to help out here.  I'd really like to  
> see this series go in via QEMU if possible.

It seems that if I just call apic_deliver_irq each time
I want to send MSI, things will work.

However, large part of the msix code is managing IRQs versus kernel,
and I'm not sure it's a wise investment of effort to rip it all out. So
IMHO, what's missing is API that abstracts managing irq routes in kvm,
specifically abstract this stuff in some way:
	kvm_get_irq_route_gsi
	kvm_add_routing_entry
	kvm_del_routing_entry
	kvm_commit_irq_routes
	kvm_set_irq
How hard is that?

For now, this API could be a stub that just stores the routes somewhere,
and set_irq would call the local apic emulation, along the lines of:

	uint8_t dest = (addr_lo & MSI_ADDR_DEST_ID_MASK)
		>> MSI_ADDR_DEST_ID_SHIFT;
	uint8_t vector = (addr_hi & MSI_DATA_VECTOR_MASK)
		>> MSI_DATA_VECTOR_SHIFT;
	uint8_t dest_mode = (addr_lo >> MSI_ADDR_DEST_MODE_SHIFT) & 0x1;
	uint8_t trigger_mode = (data >> MSI_DATA_TRIGGER_SHIFT) & 0x1;
	uint8_t delivery_mode = (data >> MSI_DATA_DELIVERY_MODE_SHIFT) &
		0x7;
	apic_deliver_irq(dest, dest_mode, delivery_mode, vector, 0,
			 trigger_mode);

I would be happy to port my msix code to work on top of this API.
Willing to help?


-- 
MST

  reply	other threads:[~2009-05-12 13:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-11 22:13 [PATCH RFC 0/2] qemu-kvm: MSI-X support Michael S. Tsirkin
2009-05-11 22:24 ` Anthony Liguori
2009-05-12 13:45   ` Michael S. Tsirkin [this message]
2009-05-13  7:17     ` 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=20090512134521.GC23796@redhat.com \
    --to=mst@redhat.com \
    --cc=anthony@codemonkey.ws \
    --cc=avi@redhat.com \
    --cc=borntraeger@de.ibm.com \
    --cc=cotte@de.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    --cc=virtualization@lists.linux-foundation.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