All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yi Min Zhao <zyimin@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v3 0/3] three zpci patches
Date: Wed, 6 Sep 2017 12:57:38 +0800	[thread overview]
Message-ID: <e699648a-f5d8-42b2-1698-06683c062b46@linux.vnet.ibm.com> (raw)
In-Reply-To: <20170905135832.70a0397c.cohuck@redhat.com>

Thank you very much!


在 2017/9/5 下午7:58, Cornelia Huck 写道:
> On Tue,  5 Sep 2017 12:12:57 +0200
> Yi Min Zhao <zyimin@linux.vnet.ibm.com> wrote:
>
>> This patch set contains three small zpci patches to fixup different issues.
>> 1) remove zpci idx from msix message, instead we could use PCIDevice's id to
>>     find zpci device in kvm_arch_fixup_msi_route()
>> 2) fixup ind_offset calculation for adapter interrupt routing entry
>> 3) introduce our own iommu_replay callback
>>
>> Yi Min Zhao (3):
>>    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  | 28 +++++++++++++++++-----------
>>   hw/s390x/s390-pci-bus.h  |  2 ++
>>   hw/s390x/s390-pci-inst.c | 24 ------------------------
>>   hw/s390x/s390-pci-stub.c |  3 ++-
>>   target/s390x/kvm.c       | 14 ++++++++------
>>   5 files changed, 29 insertions(+), 42 deletions(-)
>>
> Thanks, applied.
>
>

      reply	other threads:[~2017-09-06  4:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-05 10:12 [Qemu-devel] [PATCH v3 0/3] three zpci patches Yi Min Zhao
2017-09-05 10:12 ` [Qemu-devel] [PATCH v3 1/3] s390x/pci: remove idx from msix msg data Yi Min Zhao
2017-09-05 10:12 ` [Qemu-devel] [PATCH v3 2/3] s390x/pci: fixup ind_offset of msix routing entry Yi Min Zhao
2017-09-05 10:13 ` [Qemu-devel] [PATCH v3 3/3] s390x/pci: add iommu replay callback Yi Min Zhao
2017-09-05 11:58 ` [Qemu-devel] [PATCH v3 0/3] three zpci patches Cornelia Huck
2017-09-06  4:57   ` Yi Min Zhao [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=e699648a-f5d8-42b2-1698-06683c062b46@linux.vnet.ibm.com \
    --to=zyimin@linux.vnet.ibm.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 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.