linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peifeng Qiu <linux@qiupf.dev>
To: Linux regressions mailing list <regressions@lists.linux.dev>
Cc: bhelgaas@google.com, linux-pci@vger.kernel.org
Subject: Re: Missing sriov_numvfs after removal of EfiMemoryMappedIO from E820 map
Date: Mon, 16 Jan 2023 19:14:53 +0900	[thread overview]
Message-ID: <CAPH51bdcXFCiHrFPnMYGznsrCTOHDB0fyujFy3y5e8PWWYnnbQ@mail.gmail.com> (raw)
In-Reply-To: <2f866122-6a56-dfc7-9add-5168a4e796b2@leemhuis.info>

On Mon, Jan 16, 2023 at 12:41 AM Linux kernel regression tracking
(Thorsten Leemhuis) <regressions@leemhuis.info> wrote:
>
> Forget to mention one small detail:
>
> On 15.01.23 15:21, Linux kernel regression tracking (Thorsten Leemhuis)
> wrote:
> > [CCing the regression list, as it should be in the loop for regressions:
> > https://docs.kernel.org/admin-guide/reporting-regressions.html]
> >
> > Hi, this is your Linux kernel regression tracker.
> >
> > On 15.01.23 10:21, Peifeng Qiu wrote:
> >>
> >> I'm using a dual Xeon system with Intel e810 25G network card and make use
> >> of SRIOV feature heavily. I have a script to setup the NIC the first step is
> >> echo $VFS > /sys/class/net/$DEVNAME/device/sriov_numvfs
> >>
> >> After switching from v6.1 to v6.2-rc1 "sriov_numvfs" is no longer present. If I
> >> switch back to v6.1 it's back. Command line parameters are the same so it's
> >> most likely kernel changes. I did git bisect and found the culprit to be
> >> 07eab0901ed(efi/x86: Remove EfiMemoryMappedIO from E820 map)
> >
> > This is not my area of expertise, but there is another report about an
> > issue that was bisected to that particular commit:
> >
> > https://lore.kernel.org/lkml/ac2693d8-8ba3-72e0-5b66-b3ae008d539d@linux.intel.com/
> >
> > A fix for that one was posted here:
> >
> > https://lore.kernel.org/lkml/20230110180243.1590045-1-helgaas@kernel.org/
> >
> > You might want to look into the report and if it looks like a possible
> > duplicate give the proposed fix a try.
>
> FWIW, that patch was recently mainlined and thus will be in 6.2-rc4 that
> Linus will likely release in a few hours.
>
> Ciao, Thorsten

I just tested the latest v6.2-rc4 and I can confirm that the issue is
fixed. Thanks!

Best regards,
Peifeng Qiu

  reply	other threads:[~2023-01-16 10:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-15  9:21 Missing sriov_numvfs after removal of EfiMemoryMappedIO from E820 map Peifeng Qiu
2023-01-15 14:21 ` Linux kernel regression tracking (Thorsten Leemhuis)
2023-01-15 15:41   ` Linux kernel regression tracking (Thorsten Leemhuis)
2023-01-16 10:14     ` Peifeng Qiu [this message]
2023-01-27 11:32       ` Linux kernel regression tracking (#update)

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=CAPH51bdcXFCiHrFPnMYGznsrCTOHDB0fyujFy3y5e8PWWYnnbQ@mail.gmail.com \
    --to=linux@qiupf.dev \
    --cc=bhelgaas@google.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=regressions@lists.linux.dev \
    /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).