qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Pierre Morel <pmorel@linux.ibm.com>
To: Cornelia Huck <cohuck@redhat.com>
Cc: walling@linux.ibm.com, borntraeger@de.ibm.com, rth@twiddle.net,
	david@redhat.com, qemu-s390x@nongnu.org, qemu-devel@nongnu.org,
	pasic@linux.ibm.com, thuth@redhat.com
Subject: Re: [Qemu-devel] [PATCH v4] s390x/pci: add common function measurement block
Date: Wed, 19 Dec 2018 13:29:42 +0100	[thread overview]
Message-ID: <a6e21144-180d-f515-570c-54a351c605cf@linux.ibm.com> (raw)
In-Reply-To: <20181219104807.4c11f39f.cohuck@redhat.com>

On 19/12/2018 10:48, Cornelia Huck wrote:
> On Tue, 18 Dec 2018 18:28:59 +0100
> Pierre Morel <pmorel@linux.ibm.com> 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 successul call.
> 
> s/successul/successful/
> 
>> 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 | 129 +++++++++++++++++++++++++++++++++++++++++++++--
>>   hw/s390x/s390-pci-inst.h |   1 +
>>   4 files changed, 159 insertions(+), 4 deletions(-)
>>
> 
>> +static void fmb_update(void *opaque)
>> +{
>> +    S390PCIBusDevice *pbdev = opaque;
>> +    int64_t t = qemu_clock_get_ms(QEMU_CLOCK_VIRTUAL);
>> +    int i;
>> +
>> +    /* Update U bit */
>> +    pbdev->fmb.last_update *= 2;
>> +    pbdev->fmb.last_update |= UPDATE_U_BIT;
>> +    if (fmb_do_update(pbdev, offsetof(ZpciFmb, last_update),
>> +                      pbdev->fmb.last_update, 8)) {
>> +        return;
>> +    }
>> +
>> +    /* Update FMB sample count */
>> +    if (fmb_do_update(pbdev, offsetof(ZpciFmb, sample),
>> +                      pbdev->fmb.sample++, 4)) {
>> +        return;
>> +    }
>> +
>> +    /* Update FMB counters */
>> +    for (i = 0; i < ZPCI_FMB_CNT_MAX; i++) {
>> +        if (fmb_do_update(pbdev, offsetof(ZpciFmb, counter[i]),
>> +                          pbdev->fmb.counter[i], 8)) {
>> +            return;
>> +        }
>> +    }
>> +
>> +    /* Clear U bit and update the time */
>> +    pbdev->fmb.last_update = time2tod(qemu_clock_get_ns(QEMU_CLOCK_VIRTUAL));
>> +    pbdev->fmb.last_update *= 2;
>> +    if (fmb_do_update(pbdev, offsetof(ZpciFmb, last_update),
>> +                      pbdev->fmb.last_update, 8)) {
>> +        return;
>> +    }
>> +    timer_mod(pbdev->fmb_timer, t + DEFAULT_MUI);
>> +}
>> +
> 
> Might be better to use sizeof() instead of hard-coded values when
> calling fmb_do_update()?
> 
> Otherwise, looks good.
> 

OK, thanks, I send hopefully the last version with commit message 
corrected and sizeof instead of hard-coded values.

Regards,
Pierre


-- 
Pierre Morel
Linux/KVM/QEMU in Böblingen - Germany

      reply	other threads:[~2018-12-19 12:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-18 17:28 [Qemu-devel] [PATCH v4] s390x/pci: add common fmb Pierre Morel
2018-12-18 17:28 ` [Qemu-devel] [PATCH v4] s390x/pci: add common function measurement block Pierre Morel
2018-12-19  9:48   ` Cornelia Huck
2018-12-19 12:29     ` Pierre Morel [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=a6e21144-180d-f515-570c-54a351c605cf@linux.ibm.com \
    --to=pmorel@linux.ibm.com \
    --cc=borntraeger@de.ibm.com \
    --cc=cohuck@redhat.com \
    --cc=david@redhat.com \
    --cc=pasic@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).