qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Pavel Fedin <p.fedin@samsung.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	qemu-devel@nongnu.org, Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [Qemu-devel] [PATCH v5 0/3] Make KVM/MSI code device-ID-aware
Date: Sun, 18 Oct 2015 11:31:03 +0300	[thread overview]
Message-ID: <20151018113017-mutt-send-email-mst@redhat.com> (raw)
In-Reply-To: <cover.1444906971.git.p.fedin@samsung.com>

On Thu, Oct 15, 2015 at 02:05:14PM +0300, Pavel Fedin wrote:
> On ARM architecture ITS (Interrupt Translation Service), additionally to
> normal MSI data, uses also side-band device IDs. This series prepares the
> infrastructure to handling them.
> 
> This small series is actually an extraction from vITS support RFC
> (https://lists.gnu.org/archive/html/qemu-devel/2015-09/msg07074.html).
> Nobody reviewed it so far, however some bits of it could actually be
> applied early. This series consists only of those parts, which do not
> depend on any new unreleased kernel APIs.

Looks sane
Acked-by: Michael S. Tsirkin <mst@redhat.com>

I also reviewed the pci patch.

Thanks for your patience!


> v4 => v5:
> - pci_requester_id() moved back to architecture-independent PCI code.
> - Use pci_requester_id() in more places.
> 
> v3 => v4:
> - Rename msi_requester_id() to pci_requester_id() and move from MSI to PCI
>   code
> 
> v2 => v3:
> - Use official "requester ID" denotion everywhere. Renamed getter function
>   and MemTxAttrs field.
> 
> v1 => v2:
> - Improved commit messages, more explanations
> - msi_device_id() function made architecture-specific
> 
> Pavel Fedin (3):
>   kvm: Make KVM_CAP_SIGNAL_MSI globally available
>   hw/pci: Introduce pci_requester_id()
>   kvm: Pass PCI device pointer to MSI routing functions
> 
>  hw/i386/kvm/pci-assign.c | 11 ++++++-----
>  hw/pci/msi.c             |  2 +-
>  hw/pci/pcie_aer.c        |  2 +-
>  hw/vfio/pci.c            | 11 ++++++-----
>  hw/virtio/virtio-pci.c   |  5 +++--
>  include/exec/memattrs.h  |  4 ++--
>  include/hw/pci/pci.h     |  5 +++++
>  include/sysemu/kvm.h     | 14 ++++++++++++--
>  kvm-all.c                | 15 ++++++++-------
>  kvm-stub.c               |  5 +++--
>  10 files changed, 47 insertions(+), 27 deletions(-)
> 
> -- 
> 2.4.4

      parent reply	other threads:[~2015-10-18  8:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-15 11:05 [Qemu-devel] [PATCH v5 0/3] Make KVM/MSI code device-ID-aware Pavel Fedin
2015-10-15 11:05 ` [Qemu-devel] [PATCH v5 1/3] kvm: Make KVM_CAP_SIGNAL_MSI globally available Pavel Fedin
2015-10-15 11:05 ` [Qemu-devel] [PATCH v5 2/3] hw/pci: Introduce pci_requester_id() Pavel Fedin
2015-10-15 13:11   ` Michael S. Tsirkin
2015-10-15 13:28     ` Pavel Fedin
2015-10-18  8:29   ` Michael S. Tsirkin
2015-10-15 11:05 ` [Qemu-devel] [PATCH v5 3/3] kvm: Pass PCI device pointer to MSI routing functions Pavel Fedin
2015-10-15 11:41   ` Cornelia Huck
2015-10-15 11:59     ` Pavel Fedin
2015-10-18  8:31 ` 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=20151018113017-mutt-send-email-mst@redhat.com \
    --to=mst@redhat.com \
    --cc=p.fedin@samsung.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --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).