From: "Sebastian, Selwin" <Selwin.Sebastian@amd.com>
To: "Yigit, Ferruh" <Ferruh.Yigit@amd.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>,
David Marchand <david.marchand@redhat.com>
Subject: RE: [PATCH v3] net/axgbe: use CPUID to identify cpu
Date: Tue, 10 Oct 2023 13:38:02 +0000 [thread overview]
Message-ID: <DM4PR12MB50553F30D2FAF16A94BBDEA48DCDA@DM4PR12MB5055.namprd12.prod.outlook.com> (raw)
In-Reply-To: <38519d04-5d9a-4a04-9160-f184b125a3f2@amd.com>
[AMD Official Use Only - General]
Hi Ferruh,
Thank you. Yes, once David's patch is accepted, I will make changes to use new API.
Regards
Selwin
-----Original Message-----
From: Yigit, Ferruh <Ferruh.Yigit@amd.com>
Sent: Tuesday, October 10, 2023 6:24 PM
To: Sebastian, Selwin <Selwin.Sebastian@amd.com>; dev@dpdk.org
Cc: stable@dpdk.org; David Marchand <david.marchand@redhat.com>
Subject: Re: [PATCH v3] net/axgbe: use CPUID to identify cpu
On 10/4/2023 11:07 AM, Selwin Sebastian wrote:
> Using root complex to identify cpu will not work for vm passthrough.
> CPUID is used to get family and modelid to identify cpu
>
> Fixes: b0db927b5eba ("net/axgbe: use PCI root complex device to
> distinguish device")
> Cc: stable@dpdk.org
>
> Signed-off-by: Selwin Sebastian <selwin.sebastian@amd.com>
>
Acked-by: Ferruh Yigit <ferruh.yigit@amd.com>
Applied to dpdk-next-net/main, thanks.
Progressing with this patch for now, to not block the functionality, but when cpuid abstraction by David [1] is matured, can you please support porting this patch to new API?
[1]
[Introduce x86 specific identification
API](https://patchwork.dpdk.org/project/dpdk/list/?series=29605)
prev parent reply other threads:[~2023-10-10 13:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-04 10:07 Selwin Sebastian
2023-10-10 12:54 ` Ferruh Yigit
2023-10-10 13:38 ` Sebastian, Selwin [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=DM4PR12MB50553F30D2FAF16A94BBDEA48DCDA@DM4PR12MB5055.namprd12.prod.outlook.com \
--to=selwin.sebastian@amd.com \
--cc=Ferruh.Yigit@amd.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=stable@dpdk.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;
as well as URLs for NNTP newsgroup(s).