All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Graf <agraf@suse.de>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Alexey Kardashevskiy <aik@ozlabs.ru>,
	qemu-ppc@nongnu.org, Paul Mackerras <paulus@samba.org>,
	qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v6] kvm irqfd: support direct msimessage to irq translation
Date: Tue, 03 Sep 2013 17:36:56 +0200	[thread overview]
Message-ID: <52260218.9090405@suse.de> (raw)
In-Reply-To: <20130903081726.GB18901@redhat.com>

On 09/03/2013 10:17 AM, Michael S. Tsirkin wrote:
> On Tue, Sep 03, 2013 at 06:08:25PM +1000, Alexey Kardashevskiy wrote:
>> On PPC64 systems MSI Messages are translated to system IRQ in a PCI
>> host bridge. This is already supported for emulated MSI/MSIX but
>> not for irqfd where the current QEMU allocates IRQ numbers from
>> irqchip and maps MSIMessages to IRQ in the host kernel.
>>
>> This adds a new direct mapping flag which tells
>> the kvm_irqchip_add_msi_route() function that a new VIRQ
>> should not be allocated, instead the value from MSIMessage::data
>> should be used. It is up to the platform code to make sure that
>> this contains a valid IRQ number as sPAPR does in spapr_pci.c.
>>
>> Signed-off-by: Alexey Kardashevskiy<aik@ozlabs.ru>
> Fine with me
>
> Acked-by: Michael S. Tsirkin<mst@redhat.com>

Thanks, applied to ppc-next.


Alex

  reply	other threads:[~2013-09-03 15:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-03  8:08 [Qemu-devel] [PATCH v6] kvm irqfd: support direct msimessage to irq translation Alexey Kardashevskiy
2013-09-03  8:17 ` Michael S. Tsirkin
2013-09-03 15:36   ` Alexander Graf [this message]
2013-09-05 16:01   ` Paolo Bonzini
2013-09-05 16:03     ` Alexander Graf
2013-09-12 16:32 ` Paolo Bonzini

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=52260218.9090405@suse.de \
    --to=agraf@suse.de \
    --cc=aik@ozlabs.ru \
    --cc=mst@redhat.com \
    --cc=paulus@samba.org \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@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 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.