ntb.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Eric Pilmore <epilmore@gigaio.com>
To: Marc Smith <msmith626@gmail.com>
Cc: Logan Gunthorpe <logang@deltatee.com>,
	ntb@lists.linux.dev,  Kelvin Cao <kelvin.cao@microchip.com>,
	kelvincao@outlook.com
Subject: Re: ntb_netdev Communication Failure Issue
Date: Thu, 17 Feb 2022 08:31:22 -0800	[thread overview]
Message-ID: <CAOQPn8vVMKF8GMd2kXNCGawWZBcjOCM_7XFkq+YX2rbQ9wTOgw@mail.gmail.com> (raw)
In-Reply-To: <CAH6h+hdbOEjpU5tn+MwDm-h=47b4kzMHDZhSc51hA0VOZLp_8g@mail.gmail.com>

On Thu, Feb 17, 2022 at 7:22 AM Marc Smith <msmith626@gmail.com> wrote:
>
>
> Is it possible there are some special NTB/BIOS settings needed for
> this hardware?

I'm assuming you have the switch (NTB) properly configured so that the
respective partitions can talk to each other. The other part is
ensuring that the NT BAR did properly enumerate. If it is large, it
can become a challenge for some BIOSes to be able to enumerate it.  Do
a "sudo lspci -vvv -s <BDF>" with the BDF of the NT EP, and ensure
that the BARs (Regions 2,4) have MMIO space assigned.

When you try to run, anything interesting show up in "dmesg", such as
DMAR errors?

Eric

  reply	other threads:[~2022-02-17 16:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-16 16:16 ntb_netdev Communication Failure Issue Marc Smith
2022-02-16 17:14 ` Logan Gunthorpe
2022-02-17 15:22   ` Marc Smith
2022-02-17 16:31     ` Eric Pilmore [this message]
2022-02-17 16:49     ` Logan Gunthorpe
2022-03-09 14:35       ` Marc Smith
2022-03-09 16:52         ` Logan Gunthorpe
2022-03-09 18:26           ` Marc Smith
2022-03-09 18:31             ` Logan Gunthorpe

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=CAOQPn8vVMKF8GMd2kXNCGawWZBcjOCM_7XFkq+YX2rbQ9wTOgw@mail.gmail.com \
    --to=epilmore@gigaio.com \
    --cc=kelvin.cao@microchip.com \
    --cc=kelvincao@outlook.com \
    --cc=logang@deltatee.com \
    --cc=msmith626@gmail.com \
    --cc=ntb@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).