From: David Woodhouse <dwmw2@infradead.org>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
qemu-devel@nongnu.org,
Marcel Apfelbaum <marcel.apfelbaum@gmail.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Richard Henderson <richard.henderson@linaro.org>,
Eduardo Habkost <eduardo@habkost.net>,
Marcelo Tosatti <mtosatti@redhat.com>,
paul@xen.org
Subject: Re: [RFC] Notify IRQ sources of level interrupt ack/EOI
Date: Wed, 11 Jan 2023 20:10:22 +0000 [thread overview]
Message-ID: <07dfd533da451b1f8d6805241853bcc20c7aee78.camel@infradead.org> (raw)
In-Reply-To: <20230111130053.7564d188.alex.williamson@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 531 bytes --]
On Wed, 2023-01-11 at 13:00 -0700, Alex Williamson wrote:
>
> Careful about making too many assumptions around PCI, it's clearly the
> most used but vfio is bus agnostic and we do have vfio-platform support
> as well as some weird s390 devices. There's nothing PCI specific about
> a level triggered interrupt, so preferably all this sits a layer below
> the PCI interfaces. Thanks,
True. PCI is just the most fun to wire up the ack though, because of
the aggregation and INTX line swizzling and all that nonsense.
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5965 bytes --]
next prev parent reply other threads:[~2023-01-11 20:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-11 14:41 [RFC] Notify IRQ sources of level interrupt ack/EOI David Woodhouse
2023-01-11 16:25 ` Michael S. Tsirkin
2023-01-11 16:58 ` David Woodhouse
2023-01-11 18:29 ` Alex Williamson
2023-01-11 19:08 ` David Woodhouse
2023-01-11 19:43 ` Alex Williamson
2023-01-11 19:50 ` David Woodhouse
2023-01-11 20:00 ` Alex Williamson
2023-01-11 20:10 ` David Woodhouse [this message]
2023-01-12 8:05 ` David Woodhouse
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=07dfd533da451b1f8d6805241853bcc20c7aee78.camel@infradead.org \
--to=dwmw2@infradead.org \
--cc=alex.williamson@redhat.com \
--cc=eduardo@habkost.net \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@redhat.com \
--cc=mtosatti@redhat.com \
--cc=paul@xen.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).