From: "Michael S. Tsirkin" <mst@redhat.com>
To: Pavel Fedin <p.fedin@samsung.com>
Cc: 'Paolo Bonzini' <pbonzini@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/3] Make KVM/MSI code device-ID-aware
Date: Tue, 13 Oct 2015 18:58:58 +0300 [thread overview]
Message-ID: <20151013185850-mutt-send-email-mst@redhat.com> (raw)
In-Reply-To: <016501d105ca$564cc720$02e65560$@samsung.com>
On Tue, Oct 13, 2015 at 06:17:55PM +0300, Pavel Fedin wrote:
> Hello!
>
> > msi_device_id seems like something kvm specific.
> > Maybe not vfio, just out of pci.
>
> I've just replied the same to Paolo. msi_device_id is architecture-specific. Just there is no any other arch yet to use it except
> ARM64, therefore it is in pci. If needed, it could be moved to target-XXX.
>
> Kind regards,
> Pavel Fedin
> Expert Engineer
> Samsung Electronics Research center Russia
Pls move it.
prev parent reply other threads:[~2015-10-13 15:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-13 12:11 [Qemu-devel] [PATCH 0/3] Make KVM/MSI code device-ID-aware Pavel Fedin
2015-10-13 12:12 ` [Qemu-devel] [PATCH 1/3] kvm: Make KVM_CAP_SIGNAL_MSI globally available Pavel Fedin
2015-10-13 12:12 ` [Qemu-devel] [PATCH 2/3] hw/pci: Introduce msi_device_id() Pavel Fedin
2015-10-13 12:56 ` Michael S. Tsirkin
2015-10-13 13:24 ` Pavel Fedin
2015-10-13 12:12 ` [Qemu-devel] [PATCH 3/3] kvm: Pass PCI device pointer to MSI routing functions Pavel Fedin
2015-10-13 13:00 ` [Qemu-devel] [PATCH 0/3] Make KVM/MSI code device-ID-aware Michael S. Tsirkin
2015-10-13 13:49 ` Pavel Fedin
2015-10-13 14:03 ` Michael S. Tsirkin
2015-10-13 15:17 ` Pavel Fedin
2015-10-13 15:58 ` Michael S. Tsirkin [this message]
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=20151013185850-mutt-send-email-mst@redhat.com \
--to=mst@redhat.com \
--cc=p.fedin@samsung.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@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 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).