All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yi Min Zhao <zyimin@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org
Cc: borntraeger@de.ibm.com, pasic@linux.vnet.ibm.com,
	pmorel@linux.vnet.ibm.com, cohuck@redhat.com, agraf@suse.de,
	richard.henderson@linaro.org
Subject: Re: [Qemu-devel] [PATCH 0/4] four zpci patches
Date: Thu, 24 Aug 2017 13:20:12 +0800	[thread overview]
Message-ID: <871ef0e3-ea8b-df59-0eeb-8019b350f1d2@linux.vnet.ibm.com> (raw)
In-Reply-To: <20170823072656.3352-1-zyimin@linux.vnet.ibm.com>

Why can't I receive [Qemu-devel] prefixed patches?


在 2017/8/23 下午3:26, Yi Min Zhao 写道:
> This patch set contains four small zpci patches to fixup different issues.
> 1) fixup calculation of msix boundary
> 2) remove zpci idx from msix message, instead we could use PCIDevice's id to
>     find zpci device in kvm_arch_fixup_msi_route()
> 3) fixup ind_offset calculation for adapter interrupt routing entry
> 4) introduce our own iommu_replay callback
>
> Yi Min Zhao (4):
>    s390x/pci: fixup trap_msix()
>    s390x/pci: remove idx from msix msg data
>    s390x/pci: fixup ind_offset of msix routing entry
>    s390x/pci: add iommu replay callback
>
>   hw/s390x/s390-pci-bus.c  | 24 +++++++++++++-----------
>   hw/s390x/s390-pci-bus.h  |  2 ++
>   hw/s390x/s390-pci-inst.c | 28 ++--------------------------
>   target/s390x/kvm.c       | 11 ++++++-----
>   4 files changed, 23 insertions(+), 42 deletions(-)
>

       reply	other threads:[~2017-08-24  5:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20170823072656.3352-1-zyimin@linux.vnet.ibm.com>
2017-08-24  5:20 ` Yi Min Zhao [this message]
2017-08-24  7:13   ` [Qemu-devel] [PATCH 0/4] four zpci patches Cornelia Huck
2017-08-24  8:48     ` Yi Min Zhao
2017-08-24 16:27       ` Eric Blake
2017-08-28  3:26         ` Yi Min Zhao
2017-08-28  8:04 Yi Min Zhao

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=871ef0e3-ea8b-df59-0eeb-8019b350f1d2@linux.vnet.ibm.com \
    --to=zyimin@linux.vnet.ibm.com \
    --cc=agraf@suse.de \
    --cc=borntraeger@de.ibm.com \
    --cc=cohuck@redhat.com \
    --cc=pasic@linux.vnet.ibm.com \
    --cc=pmorel@linux.vnet.ibm.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 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.