mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Sandipan Das <sandipan.das@amd.com>
Cc: linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
	x86@kernel.org, peterz@infradead.org,
	dave.hansen@linux.intel.com, acme@kernel.org,
	mark.rutland@arm.com, alexander.shishkin@linux.intel.com,
	namhyung@kernel.org, jolsa@kernel.org, tglx@linutronix.de,
	mingo@redhat.com, pbonzini@redhat.com, jmattson@google.com,
	like.xu.linux@gmail.com, eranian@google.com, puwen@hygon.cn,
	ananth.narayan@amd.com, ravi.bangoria@amd.com,
	santosh.shukla@amd.com
Subject: Re: [PATCH v4 0/7] perf/x86/amd/core: Add AMD PerfMonV2 support
Date: Wed, 27 Apr 2022 13:37:45 +0200	[thread overview]
Message-ID: <YmkrCYZxG6cbCPGq@zn.tnic> (raw)
In-Reply-To: <cover.1651058600.git.sandipan.das@amd.com>

On Wed, Apr 27, 2022 at 05:01:42PM +0530, Sandipan Das wrote:
> Sandipan Das (7):
>   x86/cpufeatures: Add PerfMonV2 feature bit
>   x86/msr: Add PerfCntrGlobal* registers
>   perf/x86/amd/core: Detect PerfMonV2 support
>   perf/x86/amd/core: Detect available counters
>   perf/x86/amd/core: Add PerfMonV2 counter control
>   perf/x86/amd/core: Add PerfMonV2 overflow handling
>   kvm: x86/cpuid: Fix CPUID leaf 0xA
> 
>  arch/x86/events/amd/core.c         | 227 +++++++++++++++++++++++++++--
>  arch/x86/include/asm/cpufeatures.h |   2 +-
>  arch/x86/include/asm/msr-index.h   |   5 +
>  arch/x86/include/asm/perf_event.h  |  17 +++
>  arch/x86/kernel/cpu/scattered.c    |   1 +
>  arch/x86/kvm/cpuid.c               |   5 +
>  6 files changed, 240 insertions(+), 17 deletions(-)

From: Documentation/process/submitting-patches.rst

Don't get discouraged - or impatient
------------------------------------

After you have submitted your change, be patient and wait.  Reviewers are
busy people and may not get to your patch right away.

Once upon a time, patches used to disappear into the void without comment,
but the development process works more smoothly than that now.  You should
receive comments within a week or so; if that does not happen, make sure
that you have sent your patches to the right place.  Wait for a minimum of
						     ^^^^^^^^^^^^^^^^^^^^^
one week before resubmitting or pinging reviewers - possibly longer during
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
busy times like merge windows.

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette

      parent reply	other threads:[~2022-04-27 11:37 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-27 11:31 Sandipan Das
2022-04-27 11:31 ` [PATCH v4 1/7] x86/cpufeatures: Add PerfMonV2 feature bit Sandipan Das
2022-04-27 11:31 ` [PATCH v4 2/7] x86/msr: Add PerfCntrGlobal* registers Sandipan Das
2022-04-27 11:31 ` [PATCH v4 3/7] perf/x86/amd/core: Detect PerfMonV2 support Sandipan Das
2022-05-09 13:01   ` Like Xu
2022-05-09 13:08     ` Sandipan Das
2022-05-09 13:11       ` Peter Zijlstra
2022-05-10  8:36         ` Sandipan Das
2022-04-27 11:31 ` [PATCH v4 4/7] perf/x86/amd/core: Detect available counters Sandipan Das
2022-04-27 11:31 ` [PATCH v4 5/7] perf/x86/amd/core: Add PerfMonV2 counter control Sandipan Das
2022-05-09  7:05   ` Like Xu
2022-05-09  9:58     ` Sandipan Das
2022-05-09 11:24       ` Peter Zijlstra
2022-04-27 11:31 ` [PATCH v4 6/7] perf/x86/amd/core: Add PerfMonV2 overflow handling Sandipan Das
2022-04-28 13:40   ` Like Xu
2022-04-29  5:10     ` Sandipan Das
2022-04-27 11:31 ` [PATCH v4 7/7] kvm: x86/cpuid: Fix CPUID leaf 0xA Sandipan Das
2022-05-02 23:50   ` Jim Mattson
2022-05-03 12:01     ` Paolo Bonzini
2022-05-03 12:04     ` Paolo Bonzini
2022-04-27 11:37 ` Borislav Petkov [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=YmkrCYZxG6cbCPGq@zn.tnic \
    --to=bp@alien8.de \
    --cc=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=ananth.narayan@amd.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=eranian@google.com \
    --cc=jmattson@google.com \
    --cc=jolsa@kernel.org \
    --cc=like.xu.linux@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=peterz@infradead.org \
    --cc=puwen@hygon.cn \
    --cc=ravi.bangoria@amd.com \
    --cc=sandipan.das@amd.com \
    --cc=santosh.shukla@amd.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    /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®