mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mukesh Ojha <mojha@codeaurora.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: lkml <linux-kernel@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: Perf: Preserving the event across CPU hotunplug/plug and Creation of an event on offine CPU
Date: Tue, 28 May 2019 21:46:42 +0530	[thread overview]
Message-ID: <4f276f87-b6d8-f868-b3e7-9951d1383070@codeaurora.org> (raw)
In-Reply-To: <b94d3165-9870-9aa3-f76c-38383b649398@codeaurora.org>

Friendly Ping.


On 5/23/2019 6:39 PM, Mukesh Ojha wrote:
> Hi Peter/All,
>
> This is regarding the discussion happen in the past about 
> https://lkml.org/lkml/2018/2/15/1324
>
> Where the exact ask is to allow preserving and creation of events on a 
> offline CPU, so that when the CPU
> comes online it will start counting.
>
> I had a look at your patch too and resolve crash during while trying 
> to create an event on an offline cpu.
>
> In your patch,  you seem to disable event when cpu goes offline which 
> is exactly deleting the event
> from the pmu and add when it comes online, it seems to  work.
>
> But, For the purpose of allowing the creation of event while CPU is 
> offline is not able to count event while
> CPU coming online, for that i did some change, that did work.
>
> Also, I have query about the events which gets destroyed while CPU is 
> offline and we need to remove them
> once cpu comes online right ? As Raghavendra also queried the same in 
> the above thread.
>
> Don't we need  a list where we maintain the events which gets 
> destroyed while CPU is dead ?
> and clean it  up when CPU comes online ?
>
> Thanks.
> Mukesh
>
>

      reply	other threads:[~2019-05-28 16:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-23 13:09 Mukesh Ojha
2019-05-28 16:16 ` Mukesh Ojha [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=4f276f87-b6d8-f868-b3e7-9951d1383070@codeaurora.org \
    --to=mojha@codeaurora.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    /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

all inboxes | Powered by JetHome®