AMD-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "José Ramón Muñoz Pekkarinen" <koalinux-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Alex Deucher <alexdeucher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: amd-gfx list <amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>
Subject: Re: [PATCH] Look for bios sriov capabilities only if we are on Fiji or Tonga.
Date: Wed, 27 Dec 2017 16:48:06 +0200	[thread overview]
Message-ID: <4093696.CacbcO1fID@localhost> (raw)
In-Reply-To: <CADnq5_Mewg2SUFMqi0L0t7FOsD1RfKZERcK08KnybbcG=riadg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On Wednesday, 27 December 2017 09:49:40 EET Alex Deucher wrote:
> On Mon, Dec 25, 2017 at 3:49 PM, José Pekkarinen <koalinux@gmail.com> wrote:
> > Signed-off-by: José Pekkarinen <koalinux@gmail.com>
> 
> NACK.  This will break vega10.  The virtualization table only exists
> on sr-iov capable cards so the checks are safe on all asics.
> 
> Alex

	Yes, true, for some time I wrongly believed it activates 
AMDGPU_SRIOV_CAPS_IS_VF and allows getting into amdgpu_sriov_vf checks. 
Hopefully not the case.

	Thanks again!

	José.
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

      parent reply	other threads:[~2017-12-27 14:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-25 20:49 [PATCH] Look for bios sriov capabilities only if we are on Fiji or Tonga José Pekkarinen
     [not found] ` <20171225204947.9950-1-koalinux-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-12-27  7:49   ` Alex Deucher
     [not found]     ` <CADnq5_Mewg2SUFMqi0L0t7FOsD1RfKZERcK08KnybbcG=riadg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-12-27 14:48       ` José Ramón Muñoz Pekkarinen [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=4093696.CacbcO1fID@localhost \
    --to=koalinux-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=alexdeucher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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