From: "Morten Brørup" <mb@smartsharesystems.com>
To: "Tummala, Sivaprasad" <Sivaprasad.Tummala@amd.com>,
"Konstantin Ananyev" <konstantin.ananyev@huawei.com>,
"Thomas Monjalon" <thomas@monjalon.net>,
"Kevin Traynor" <ktraynor@redhat.com>,
"David Marchand" <david.marchand@redhat.com>,
"Yigit, Ferruh" <Ferruh.Yigit@amd.com>,
<bruce.richardson@intel.com>, <konstantin.v.ananyev@yandex.ru>,
<maxime.coquelin@redhat.com>, "Aaron Conole" <aconole@redhat.com>
Cc: <dev@dpdk.org>
Subject: RE: [PATCH] config/x86: config support for AMD EPYC processors
Date: Wed, 8 Nov 2023 14:06:47 +0100 [thread overview]
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35E9EFF3@smartserver.smartshare.dk> (raw)
In-Reply-To: <DM3PR12MB9286258E81843A1940EBE35986A8A@DM3PR12MB9286.namprd12.prod.outlook.com>
> From: Tummala, Sivaprasad [mailto:Sivaprasad.Tummala@amd.com]
> Sent: Wednesday, 8 November 2023 13.24
>
> [AMD Official Use Only - General]
>
> Hi Konstantin, Morten,
>
> > From: Konstantin Ananyev <konstantin.ananyev@huawei.com>
> > Sent: Tuesday, November 7, 2023 8:03 PM
> >
> >
> > > > I suppose for 23.11 we have not much choice but accept that patch
> > > > as it is.
> > >
> > > No. They agreed in the techboard meeting to rework it for cross
> compile.
> >
> > Ah, yes, cross-builds, nearly forgot about them.
> > I suppose yes, you are right, it needs to be supported for
> completeness.
> >
>
> Yes, currently the patch is targeted to support max lcores selection
> only for native builds.
> Cross-compilation works as it is now.
>
> Once this patch is merged in this release, we plan to extend for cross
> builds in the coming releases.
OK, I'll accept this approach.
Acked-by: Morten Brørup <mb@smartsharesystems.com>
next prev parent reply other threads:[~2023-11-08 13:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-25 15:10 Sivaprasad Tummala
2023-10-06 7:50 ` David Marchand
2023-10-16 5:14 ` Tummala, Sivaprasad
2023-10-16 5:20 ` Tummala, Sivaprasad
2023-10-17 9:45 ` Kevin Traynor
2023-10-17 10:27 ` Morten Brørup
2023-11-06 21:05 ` Thomas Monjalon
2023-11-06 22:17 ` Morten Brørup
2023-11-07 13:13 ` Konstantin Ananyev
2023-11-07 13:30 ` Morten Brørup
2023-11-07 14:32 ` Konstantin Ananyev
2023-11-08 12:24 ` Tummala, Sivaprasad
2023-11-08 13:06 ` Morten Brørup [this message]
2023-11-09 16:43 ` Konstantin Ananyev
2023-10-17 10:58 ` Ferruh Yigit
2023-11-07 12:59 ` Konstantin Ananyev
2023-11-12 13:48 ` Thomas Monjalon
2023-12-20 7:10 Sivaprasad Tummala
2023-12-20 7:27 ` Morten Brørup
2023-12-20 9:22 ` Tummala, Sivaprasad
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=98CBD80474FA8B44BF855DF32C47DC35E9EFF3@smartserver.smartshare.dk \
--to=mb@smartsharesystems.com \
--cc=Ferruh.Yigit@amd.com \
--cc=Sivaprasad.Tummala@amd.com \
--cc=aconole@redhat.com \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@huawei.com \
--cc=konstantin.v.ananyev@yandex.ru \
--cc=ktraynor@redhat.com \
--cc=maxime.coquelin@redhat.com \
--cc=thomas@monjalon.net \
/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 NNTP newsgroup(s).