From: Borislav Petkov <bp@alien8.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: x86-ml <x86@kernel.org>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] perf/urgent for v6.2-rc4
Date: Sun, 15 Jan 2023 13:31:06 +0100 [thread overview]
Message-ID: <Y8PyCsf/rruY0TM1@zn.tnic> (raw)
In-Reply-To: <Y8PwPKu2/SfWMdn6@zn.tnic>
Pls ignore this one too - you have it already.
Sorry for the noise.
On Sun, Jan 15, 2023 at 01:23:24PM +0100, Borislav Petkov wrote:
> Hi Linus,
>
> please pull a couple of urgent perf fixes for 6.2.
>
> Thx.
>
> ---
>
> The following changes since commit b7bfaa761d760e72a969d116517eaa12e404c262:
>
> Linux 6.2-rc3 (2023-01-08 11:49:43 -0600)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tags/perf_urgent_for_v6.2_rc4
>
> for you to fetch changes up to 5268a2842066c227e6ccd94bac562f1e1000244f:
>
> perf/x86/intel/uncore: Add Emerald Rapids (2023-01-09 12:00:58 +0100)
>
> ----------------------------------------------------------------
> - Add new Meteor Lake and Emerald Rapids support to the model checking
> and detection logic
>
> ----------------------------------------------------------------
> Kan Liang (4):
> perf/x86/cstate: Add Meteor Lake support
> perf/x86/msr: Add Meteor Lake support
> perf/x86/msr: Add Emerald Rapids
> perf/x86/intel/uncore: Add Emerald Rapids
>
> arch/x86/events/intel/cstate.c | 21 ++++++++++++---------
> arch/x86/events/intel/uncore.c | 1 +
> arch/x86/events/msr.c | 3 +++
> 3 files changed, 16 insertions(+), 9 deletions(-)
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
prev parent reply other threads:[~2023-01-15 12:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-15 12:23 [GIT PULL] perf/urgent for v6.2-rc4 Borislav Petkov
2023-01-15 12:30 ` pr-tracker-bot
2023-01-15 12:31 ` 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=Y8PyCsf/rruY0TM1@zn.tnic \
--to=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--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