public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Richter <robert.richter@amd.com>
To: Heinz Graalfs <graalfs@linux.vnet.ibm.com>
Cc: "mingo@elte.hu" <mingo@elte.hu>,
	"oprofile-list@lists.sf.net" <oprofile-list@lists.sf.net>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-s390@vger.kernel.org" <linux-s390@vger.kernel.org>,
	"borntraeger@de.ibm.com" <borntraeger@de.ibm.com>,
	"schwidefsky@de.ibm.com" <schwidefsky@de.ibm.com>,
	"heiko.carstens@de.ibm.com" <heiko.carstens@de.ibm.com>,
	Mahesh Salgaonkar <mahesh@linux.vnet.ibm.com>,
	Maran Pakkirisamy <maranp@linux.vnet.ibm.com>
Subject: Re: [patch v2 1/3] This patch adds support for hardware based sampling on System z processors (models z10 and up)
Date: Fri, 25 Mar 2011 12:00:13 +0100	[thread overview]
Message-ID: <20110325110013.GW31407@erda.amd.com> (raw)
In-Reply-To: <20110121100841.879534437@linux.vnet.ibm.com>

On 21.01.11 05:06:52, Heinz Graalfs wrote:
> From: Heinz Graalfs <graalfs@linux.vnet.ibm.com>
> 
> System z's hardware sampling is described in detail in:
> 
>    SA23-2260-01 "The Load-Program-Parameter and CPU-Measurement Facilities"
> 
> The patch introduces
>  - support for System z's hardware sampler in OProfile's kernel module
>  - it adds functions that control all hardware sampling related operations as
>   - checking if hardware sampling feature is available
>     - ie: on System z models z10 and up, in LPAR mode only, and authorised during LPAR activation
>   - allocating memory for the hardware sampling feature
>   - starting/stopping hardware sampling
> 
> All functions required to start and stop hardware sampling have to be
> invoked by the oprofile kernel module as provided by the other patches of this patch set.
> 
> In case hardware based sampling cannot be setup standard timer based sampling is used by OProfile.
> 
> Signed-off-by: Mahesh Salgaonkar <mahesh@linux.vnet.ibm.com>
> Signed-off-by: Maran Pakkirisamy <maranp@linux.vnet.ibm.com>
> Signed-off-by: Heinz Graalfs <graalfs@linux.vnet.ibm.com>
> ---
>  arch/Kconfig                   |    3
>  arch/s390/Kconfig              |    1
>  arch/s390/oprofile/hwsampler.c | 1256 +++++++++++++++++++++++++++++++++++++++++
>  arch/s390/oprofile/hwsampler.h |  113 +++
>  4 files changed, 1373 insertions(+)

> +int hwsampler_setup()
> +{
> +       int rc;
> +       int cpu;
> +       struct hws_cpu_buffer *cb;
> +
> +       mutex_lock(&hws_sem);
> +
> +       rc = -EINVAL;
> +       if (hws_state)
> +               goto setup_exit;
> +
> +       hws_state = HWS_INIT;

hws_state is never set to zero again, so we will pass this point only
one time, even after hwsampler_shutdown(). Is this intended? Only
loading and unloading this as module would work.

Maybe we clear hws_state in hwsampler_shutdown()?

-Robert

> +
> +       init_all_cpu_buffers();
> +
> +       rc = check_hardware_prerequisites();
> +       if (rc)
> +               goto setup_exit;
> +
> +       rc = check_qsi_on_setup();
> +       if (rc)
> +               goto setup_exit;
> +
> +       rc = -EINVAL;
> +       hws_wq = create_workqueue("hwsampler");
> +       if (!hws_wq)
> +               goto setup_exit;
> +
> +       register_cpu_notifier(&hws_cpu_notifier);
> +
> +       for_each_online_cpu(cpu) {
> +               cb = &per_cpu(sampler_cpu_buffer, cpu);
> +               INIT_WORK(&cb->worker, worker);
> +               rc = smp_ctl_qsi(cpu);
> +               WARN_ON(rc);
> +               if (min_sampler_rate != cb->qsi.min_sampl_rate) {
> +                       if (min_sampler_rate) {
> +                               printk(KERN_WARNING
> +                                       "hwsampler: different min sampler rate values.\n");
> +                               if (min_sampler_rate < cb->qsi.min_sampl_rate)
> +                                       min_sampler_rate =
> +                                               cb->qsi.min_sampl_rate;
> +                       } else
> +                               min_sampler_rate = cb->qsi.min_sampl_rate;
> +               }
> +               if (max_sampler_rate != cb->qsi.max_sampl_rate) {
> +                       if (max_sampler_rate) {
> +                               printk(KERN_WARNING
> +                                       "hwsampler: different max sampler rate values.\n");
> +                               if (max_sampler_rate > cb->qsi.max_sampl_rate)
> +                                       max_sampler_rate =
> +                                               cb->qsi.max_sampl_rate;
> +                       } else
> +                               max_sampler_rate = cb->qsi.max_sampl_rate;
> +               }
> +       }
> +       register_external_interrupt(0x1407, hws_ext_handler);
> +
> +       hws_state = HWS_DEALLOCATED;
> +       rc = 0;
> +
> +setup_exit:
> +       mutex_unlock(&hws_sem);
> +       return rc;
> +}
> +
> +int hwsampler_shutdown()
> +{
> +       int rc;
> +
> +       mutex_lock(&hws_sem);
> +
> +       rc = -EINVAL;
> +       if (hws_state == HWS_DEALLOCATED || hws_state == HWS_STOPPED) {
> +               mutex_unlock(&hws_sem);
> +
> +               if (hws_wq)
> +                       flush_workqueue(hws_wq);
> +
> +               mutex_lock(&hws_sem);
> +
> +               if (hws_state == HWS_STOPPED) {
> +                       smp_ctl_clear_bit(0, 5); /* set bit 58 CR0 off */
> +                       deallocate_sdbt();
> +               }
> +               if (hws_wq) {
> +                       destroy_workqueue(hws_wq);
> +                       hws_wq = NULL;
> +               }
> +
> +               unregister_external_interrupt(0x1407, hws_ext_handler);
> +               hws_state = HWS_INIT;
> +               rc = 0;
> +       }
> +       mutex_unlock(&hws_sem);
> +
> +       unregister_cpu_notifier(&hws_cpu_notifier);
> +
> +       return rc;
> +}

-- 
Advanced Micro Devices, Inc.
Operating System Research Center


  parent reply	other threads:[~2011-03-25 11:00 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-21 10:06 [patch v2 0/3] OProfile support for System z's hardware sampling Heinz Graalfs
2011-01-21 10:06 ` [patch v2 1/3] This patch adds support for hardware based sampling on System z processors (models z10 and up) Heinz Graalfs
2011-02-14 18:57   ` Robert Richter
2011-03-25 11:00   ` Robert Richter [this message]
2011-03-29 12:38     ` Heinz Graalfs
2011-01-21 10:06 ` [patch v2 2/3] This patch enhances OProfile to support System zs hardware sampling feature Heinz Graalfs
2011-02-14 19:01   ` Robert Richter
2011-02-14 19:03     ` Robert Richter
2011-02-14 19:05     ` [PATCH] oprofile, s390: Rework hwsampler implementation Robert Richter
2011-02-14 19:07     ` [PATCH] oprofile, s390: Fix section mismatch of function hws_cpu_callback() Robert Richter
2011-01-21 10:06 ` [patch v2 3/3] This patch introduces a new oprofile sample add function (oprofile_add_ext_hw_sample) Heinz Graalfs
2011-02-14 18:55   ` Robert Richter
2011-02-07  8:23 ` [patch v2 0/3] OProfile support for System z's hardware sampling Heinz Graalfs
2011-02-14 19:42 ` Robert Richter
2011-02-15  7:17   ` Heiko Carstens
2011-02-15 16:59   ` Heinz Graalfs
2011-02-15 17:29     ` Robert Richter

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=20110325110013.GW31407@erda.amd.com \
    --to=robert.richter@amd.com \
    --cc=borntraeger@de.ibm.com \
    --cc=graalfs@linux.vnet.ibm.com \
    --cc=heiko.carstens@de.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=mahesh@linux.vnet.ibm.com \
    --cc=maranp@linux.vnet.ibm.com \
    --cc=mingo@elte.hu \
    --cc=oprofile-list@lists.sf.net \
    --cc=schwidefsky@de.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