Re: [Qemu-devel] [PATCH 0/4] four zpci patches

Re: [Qemu-devel] [PATCH 0/4] four zpci patches

[Yi Min Zhao]

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(-)
>

Re: [Qemu-devel] [PATCH 0/4] four zpci patches

[Cornelia Huck]

On Thu, 24 Aug 2017 13:20:12 +0800
Yi Min Zhao <zyimin@linux.vnet.ibm.com> wrote:

> 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(-)
> >  
> 

Well, I did not get any of your original patches, just this reply...
seem to be stuck somewhere?

Re: [Qemu-devel] [PATCH 0/4] four zpci patches

[Yi Min Zhao]

在 2017/8/24 下午3:13, Cornelia Huck 写道:
> On Thu, 24 Aug 2017 13:20:12 +0800
> Yi Min Zhao <zyimin@linux.vnet.ibm.com> wrote:
>
>> 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(-)
>>>   
> Well, I did not get any of your original patches, just this reply...
> seem to be stuck somewhere?
>
>
I sent patches to qemu-devel@nongnu.org and cc you also myself.
But what I received looks like CC ones, no [Qemu-devel] prefix.
Let me send them again. I'm not sure the reason.

Re: [Qemu-devel] [PATCH 0/4] four zpci patches

[Eric Blake]

[-- Attachment #1: Type: text/plain, Size: 1974 bytes --]

On 08/24/2017 03:48 AM, Yi Min Zhao wrote:
> 
> 
> 在 2017/8/24 下午3:13, Cornelia Huck 写道:
>> On Thu, 24 Aug 2017 13:20:12 +0800
>> Yi Min Zhao <zyimin@linux.vnet.ibm.com> wrote:
>>
>>> Why can't I receive [Qemu-devel] prefixed patches?

>>
> I sent patches to qemu-devel@nongnu.org and cc you also myself.
> But what I received looks like CC ones, no [Qemu-devel] prefix.

You can tell mailman whether you want to receive copies of mails through
the list even when you are listed in cc (defaults to on, but some people
like myself set it off to reduce mail); if you switch that option in
your subscription settings, then you will not see the [Qemu-devel]
prefix on any mail where you were cc'd.  [side note: turning off copies
of mail where you are cc'd triggers what I consider to be a mailman bug:
it actively rewrites the to/cc of the email to omit your address in the
copy it sends to the list, which means people who follow up to the list
no longer cc you, and do not know that you were cc'd in the first place]

Furthermore, there may be other places along the way that do data
de-duplication.  For example, anyone subscribing via a gmail.com address
gets at most one copy of a message based on the message-id; if they are
subscribed to the mailing list and also get a cc of a given message,
only one of those copies will show up (because google suppressed the
second copy with the same message-id, even though the subject lines are
different); the one copy is often (but not always) the one without the
[Qemu-devel] prefix because cc'd mail goes through less processing and
thus tends to arrive sooner than the copy sent through mailman.  [side
note: google calls de-duplication a feature, but you can't turn it off,
and it's one of the reasons that I don't use google for my personal email]

-- 
Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3266
Virtualization:  qemu.org | libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 619 bytes --]

Re: [Qemu-devel] [PATCH 0/4] four zpci patches

[Yi Min Zhao]

在 2017/8/25 上午12:27, Eric Blake 写道:
> On 08/24/2017 03:48 AM, Yi Min Zhao wrote:
>>
>> 在 2017/8/24 下午3:13, Cornelia Huck 写道:
>>> On Thu, 24 Aug 2017 13:20:12 +0800
>>> Yi Min Zhao <zyimin@linux.vnet.ibm.com> wrote:
>>>
>>>> Why can't I receive [Qemu-devel] prefixed patches?
>> I sent patches to qemu-devel@nongnu.org and cc you also myself.
>> But what I received looks like CC ones, no [Qemu-devel] prefix.
> You can tell mailman whether you want to receive copies of mails through
> the list even when you are listed in cc (defaults to on, but some people
> like myself set it off to reduce mail); if you switch that option in
> your subscription settings, then you will not see the [Qemu-devel]
> prefix on any mail where you were cc'd.  [side note: turning off copies
> of mail where you are cc'd triggers what I consider to be a mailman bug:
> it actively rewrites the to/cc of the email to omit your address in the
> copy it sends to the list, which means people who follow up to the list
> no longer cc you, and do not know that you were cc'd in the first place]
I didn't tell mailman anything. So I think the receiving copies setting 
is turned on.
What I can receive is only from cc. But as what Conny said, it seems 
that other external reviewers
in cc list didn't receive any mail unless I replied a mail.
> Furthermore, there may be other places along the way that do data
> de-duplication.  For example, anyone subscribing via a gmail.com address
> gets at most one copy of a message based on the message-id; if they are
> subscribed to the mailing list and also get a cc of a given message,
> only one of those copies will show up (because google suppressed the
> second copy with the same message-id, even though the subject lines are
> different); the one copy is often (but not always) the one without the
> [Qemu-devel] prefix because cc'd mail goes through less processing and
> thus tends to arrive sooner than the copy sent through mailman.  [side
> note: google calls de-duplication a feature, but you can't turn it off,
> and it's one of the reasons that I don't use google for my personal email]
>

[Qemu-devel] [PATCH 0/4] four zpci patches

[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(-)

-- 
2.11.0 (Apple Git-81)