From: Paolo Bonzini <pbonzini@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Thomas Huth <thuth@redhat.com>,
Marcel Apfelbaum <marcel.apfelbaum@gmail.com>,
qemu-devel@nongnu.org, qemu-trivial@nongnu.org,
yang zhong <yang.zhong@intel.com>
Subject: Re: [Qemu-devel] [PATCH] hw/pci/pci-stub: Add msi_enabled() and msi_notify() to the pci stubs
Date: Tue, 19 Feb 2019 18:19:30 -0500 (EST) [thread overview]
Message-ID: <1590333482.2281318.1550618370282.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20190219152040-mutt-send-email-mst@kernel.org>
> > Makes sense, but it is also abstraction time. :) What if instead there
> > was a function
> >
> > void msi_allocate_irqs(PCIDevice *pdev, int num, bool fallback_to_intx);
> >
> > and then ich.c did
> >
> > irqs = msi_allocate_irqs(pdev, 1, true);
> > s->irq = irqs[0];
> > g_free(irqs);
> >
> > ? "if msi_enabled raise MSI else raise INTX" is really a common idiom.
> >
> > Thanks,
> >
> > Paolo
>
> Maybe it is but the specific issue is not about fallback to INTX of PCI
> (is the fallback broken for ahci? I don't know).
It works, the above is just a new abstraction.
> The trick is there's no pdev at all.
The trick :) is that in ich.c there is a pdev. Right now we are assigning to
s->irq either the INTX irq (if PCI) or a sysbus irq (if sysbus), but then
we need to know about MSI with a wrapper around s->irq.
Instead, my suggestion is to put the wrapper in the PCI core as a qemu_irq
callback---or perhaps in ich.c, but anyway ahci.c should not care that there
could be a PCI AHCI device and it would have two different interrupt modes.
In fact, doing this would also remove the need for s->container, I think.
Paolo
next prev parent reply other threads:[~2019-02-19 23:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-19 16:07 [Qemu-devel] [PATCH] hw/pci/pci-stub: Add msi_enabled() and msi_notify() to the pci stubs Thomas Huth
2019-02-19 17:23 ` Philippe Mathieu-Daudé
2019-02-19 18:24 ` Paolo Bonzini
2019-02-19 20:23 ` Michael S. Tsirkin
2019-02-19 23:19 ` Paolo Bonzini [this message]
2019-02-20 3:35 ` Michael S. Tsirkin
2019-02-19 20:19 ` Michael S. Tsirkin
2019-02-20 6:24 ` Thomas Huth
2019-02-21 16:55 ` Michael S. Tsirkin
2019-02-21 18:00 ` 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=1590333482.2281318.1550618370282.JavaMail.zimbra@redhat.com \
--to=pbonzini@redhat.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=thuth@redhat.com \
--cc=yang.zhong@intel.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;
as well as URLs for NNTP newsgroup(s).