qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: David Hildenbrand <david@redhat.com>
Cc: pmorel@linux.ibm.com, walling@linux.ibm.com,
	borntraeger@de.ibm.com, rth@twiddle.net, qemu-s390x@nongnu.org,
	qemu-devel@nongnu.org, pasic@linux.ibm.com, thuth@redhat.com
Subject: Re: [Qemu-devel] [PATCH v7] s390x/pci: add common function measurement block
Date: Mon, 14 Jan 2019 10:44:36 +0100	[thread overview]
Message-ID: <20190114104436.46ab183c.cohuck@redhat.com> (raw)
In-Reply-To: <879a92e3-cfd9-b26f-a45a-ab8c20c5ffaa@redhat.com>

On Mon, 14 Jan 2019 10:23:58 +0100
David Hildenbrand <david@redhat.com> wrote:

> On 14.01.19 10:18, Pierre Morel wrote:
> > On 09/01/2019 12:43, David Hildenbrand wrote:  
> >> On 09.01.19 12:29, David Hildenbrand wrote:  
> >>> On 08.01.19 18:37, Pierre Morel wrote:  
> >>>> From: Yi Min Zhao <zyimin@linux.ibm.com>
> >>>>
> >>>> Common function measurement block is used to report zPCI internal
> >>>> counters of successful pcilg/stg/stb and rpcit instructions to
> >>>> a memory location provided by the program.
> >>>>
> >>>> This patch introduces a new ZpciFmb structure and schedules a timer
> >>>> callback to copy the zPCI measures to the FMB in the guest memory
> >>>> at an interval time set to 4s.
> >>>>
> >>>> An error while attemping to update the FMB, would generate an error
> >>>> event to the guest.
> >>>>
> >>>> The pcilg/stg/stb and rpcit interception handlers increase the
> >>>> related counter on a successful call.
> >>>> The guest shall pass a null FMBA (FMB address) in the FIB (Function
> >>>> Information Block) when it issues a Modify PCI Function Control
> >>>> instruction to switch off FMB and stop the corresponding timer.
> >>>>
> >>>> Signed-off-by: Yi Min Zhao <zyimin@linux.ibm.com>
> >>>> Signed-off-by: Pierre Morel <pmorel@linux.ibm.com>
> >>>> ---
> >>>>   hw/s390x/s390-pci-bus.c  |   4 +-
> >>>>   hw/s390x/s390-pci-bus.h  |  29 +++++++++++
> >>>>   hw/s390x/s390-pci-inst.c | 133 +++++++++++++++++++++++++++++++++++++++++++++--
> >>>>   hw/s390x/s390-pci-inst.h |   1 +
> >>>>   4 files changed, 163 insertions(+), 4 deletions(-)
> >>>>
> >>>> diff --git a/hw/s390x/s390-pci-bus.c b/hw/s390x/s390-pci-bus.c
> >>>> index 060ff06..f0d34dd 100644
> >>>> --- a/hw/s390x/s390-pci-bus.c
> >>>> +++ b/hw/s390x/s390-pci-bus.c
> >>>> @@ -989,6 +989,7 @@ static void s390_pcihost_hot_unplug(HotplugHandler *hotplug_dev,
> >>>>       bus = pci_get_bus(pci_dev);
> >>>>       devfn = pci_dev->devfn;
> >>>>       object_unparent(OBJECT(pci_dev));
> >>>> +    fmb_timer_free(pbdev);  
> >>>
> >>> I still think this is the wrong place. it has nothing to do with
> >>> hotplug/unplug. This belongs into unrealize/finalize.
> >>>
> >>>  
> >>
> >> ... but I see the issue. It boils down to the bad design of zPCI. The
> >> PCI device has no clue about the pbdev. So this has to stay here because
> >> in unrealize of pbdev it would be wrong and into unrealize of pci_dev,
> >> we can't move it.
> >>  
> > 
> > OK, thanks.
> > So is it a ack from you?  
> 
> Acked-by: David Hildenbrand <david@redhat.com>
> 
> :)

Great!

Still waiting for an ack from Collin (nudge, nudge :) before applying
this.

  parent reply	other threads:[~2019-01-14  9:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-08 17:37 [Qemu-devel] [PATCH v7] s390x/pci: add common fmb Pierre Morel
2019-01-08 17:37 ` [Qemu-devel] [PATCH v7] s390x/pci: add common function measurement block Pierre Morel
2019-01-09 11:29   ` David Hildenbrand
2019-01-09 11:43     ` David Hildenbrand
2019-01-14  9:18       ` Pierre Morel
2019-01-14  9:23         ` David Hildenbrand
2019-01-14  9:31           ` Pierre Morel
2019-01-14  9:44           ` Cornelia Huck [this message]
2019-01-17 15:44             ` [Qemu-devel] [qemu-s390x] " Collin Walling
2019-01-17 16:37   ` [Qemu-devel] " Cornelia Huck

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=20190114104436.46ab183c.cohuck@redhat.com \
    --to=cohuck@redhat.com \
    --cc=borntraeger@de.ibm.com \
    --cc=david@redhat.com \
    --cc=pasic@linux.ibm.com \
    --cc=pmorel@linux.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-s390x@nongnu.org \
    --cc=rth@twiddle.net \
    --cc=thuth@redhat.com \
    --cc=walling@linux.ibm.com \
    /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).