DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Thinh Tran <thinhtr@linux.vnet.ibm.com>
Cc: dev <dev@dpdk.org>, David Christensen <drc@linux.vnet.ibm.com>
Subject: Re: [dpdk-dev] [PATCH v2] build/ppc: enable build support for Power10
Date: Thu, 14 Oct 2021 17:29:23 +0200	[thread overview]
Message-ID: <CAJFAV8wuMk-Z45mg=qgeprXQuZCbFYArCO270-6uCddqTFYwiQ@mail.gmail.com> (raw)
In-Reply-To: <20211012185432.647898-1-thinhtr@linux.vnet.ibm.com>

On Tue, Oct 12, 2021 at 8:55 PM Thinh Tran <thinhtr@linux.vnet.ibm.com> wrote:
>
> For native build, enabling building the highest cpu_instruction_set
> supported by the build host, including the new POWER10.
>
> For cross compile, verifying that the compiler supports the
> cpu_instruction_set specified in the cross-file
>
> Signed-off-by: Thinh Tran <thinhtr@linux.vnet.ibm.com>
> Reviewed-by: David Christensen <drc@linux.vnet.ibm.com>

I could not test for Power10 with my toolchain
Checking if "Detect P10" compiles: NO
config/ppc/meson.build:53:18: ERROR: Problem encountered: POWER10
requested but not supported

In any case, applied, thanks.

>
>
> v2:
> * resubmit to trigger the rebuild on the current head of repo which
>   should have the fix for the build issue reported in Bug 817

This comment should be an annotation.
https://doc.dpdk.org/guides/contributing/patches.html#creating-patches

Dropped from commitlog.


-- 
David Marchand


      reply	other threads:[~2021-10-14 15:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-30  0:08 [dpdk-dev] [PATCH] " Thinh Tran
2021-10-12 18:54 ` [dpdk-dev] [PATCH v2] " Thinh Tran
2021-10-14 15:29   ` David Marchand [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='CAJFAV8wuMk-Z45mg=qgeprXQuZCbFYArCO270-6uCddqTFYwiQ@mail.gmail.com' \
    --to=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=drc@linux.vnet.ibm.com \
    --cc=thinhtr@linux.vnet.ibm.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 NNTP newsgroup(s).