public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Biener <richard.guenther@gmail.com>
To: "Anbazhagan, Karthiban" <Karthiban.Anbazhagan@amd.com>,
	Jan Hubicka <hubicka@ucw.cz>,  Uros Bizjak <ubizjak@gmail.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
	 "Kumar, Venkataramanan" <Venkataramanan.Kumar@amd.com>,
	 "Joshi, Tejas Sanjay" <TejasSanjay.Joshi@amd.com>,
	 "honza.hubicka@gmail.com" <honza.hubicka@gmail.com>,
	 "Nagarajan, Muthu kumar raj" <Muthukumarraj.Nagarajan@amd.com>,
	 "Gopalasubramanian, Ganesh" <Ganesh.Gopalasubramanian@amd.com>
Subject: Re: [PATCH] [X86_64]: Enable support for next generation AMD Zen5 CPU with znver5 scheduler Model
Date: Mon, 12 Feb 2024 08:51:18 +0100	[thread overview]
Message-ID: <CAFiYyc03BYpBT6V0f1Ved9y_ihkp+W6Y0404_B_OzJODn9tPPw@mail.gmail.com> (raw)
In-Reply-To: <LV2PR12MB5751A32C4B6E7EC9F724F1B3844A2@LV2PR12MB5751.namprd12.prod.outlook.com>

On Sat, Feb 10, 2024 at 1:55 PM Anbazhagan, Karthiban
<Karthiban.Anbazhagan@amd.com> wrote:
>
> [Public]
>
>
> Hi all,
>
>
>
> PFA, the patch that enables support for the next generation AMD Zen5 CPU via -march=znver5 with basic znver5 scheduler Model.
>
> We may update the scheduler model going forward.
>
>
>
> Good for trunk?

I'll note that gmail flagged this as spam, in case there's no response
from maintainers
I suggest to re-send.

The patch itself looks straight forward, I'll leave review to Honza/Uros though.

I'll note we have around eight processor_type left before eventually overflowing
the m_PROCESSOR mask ...

Thanks,
Richard.

> Thanks and Regards
>
> Karthiban
>
>
>
>
>
> Resending the patch, as unable to inline the patch here.
>
> reason : awaits moderator approval
>
> Message body is too big: 601858 bytes with a limit of 400 KB
>
>

  reply	other threads:[~2024-02-12  7:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-10 10:04 Anbazhagan, Karthiban
2024-02-10 12:54 ` Anbazhagan, Karthiban
2024-02-12  7:51   ` Richard Biener [this message]
2024-02-12 15:59   ` Jan Hubicka
2024-02-14 13:23     ` Anbazhagan, Karthiban
2024-02-14 13:29       ` Jan Hubicka
2024-02-22 18:29       ` Anbazhagan, Karthiban
2024-03-18 11:04         ` Mikael Morin
2024-03-18 13:21           ` Jan Hubicka
2024-03-11 22:41 ` Jan Hubicka
2024-03-12 11:22   ` Kumar, Venkataramanan

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=CAFiYyc03BYpBT6V0f1Ved9y_ihkp+W6Y0404_B_OzJODn9tPPw@mail.gmail.com \
    --to=richard.guenther@gmail.com \
    --cc=Ganesh.Gopalasubramanian@amd.com \
    --cc=Karthiban.Anbazhagan@amd.com \
    --cc=Muthukumarraj.Nagarajan@amd.com \
    --cc=TejasSanjay.Joshi@amd.com \
    --cc=Venkataramanan.Kumar@amd.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=honza.hubicka@gmail.com \
    --cc=hubicka@ucw.cz \
    --cc=ubizjak@gmail.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 read-only IMAP folder(s) and NNTP newsgroup(s).