All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dr. Greg" <greg@enjellic.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: xen-devel@lists.xen.org
Subject: Re: IGD pass-through failures since 4.10.
Date: Thu, 24 Feb 2022 18:16:02 -0600	[thread overview]
Message-ID: <20220225001602.GB5755@wind.enjellic.com> (raw)
In-Reply-To: <b9a77707-5d93-050a-f9ee-da284dbd0eac@suse.com>

On Wed, Feb 23, 2022 at 09:59:48AM +0100, Jan Beulich wrote:

Hi, I hope the end of the week is going well for everyone.

> On 22.02.2022 19:52, Dr. Greg wrote:
> > On Fri, Feb 18, 2022 at 08:04:14AM +0100, Jan Beulich wrote:
> >> On 17.02.2022 21:15, Dr. Greg wrote:
> >>> On Mon, Feb 14, 2022 at 09:56:34AM +0100, Jan Beulich wrote:
> >>> In the case of the logs above, the following command sequence is being
> >>> executed upon termination of the domain:
> >>>
> >>> # Unbind devices.
> >>> echo 0000:00:14.0 >| /sys/bus/pci/drivers/pciback/unbind
> >>> echo 0000:00:02.0 >| /sys/bus/pci/drivers/pciback/unbind
> >>>
> >>> # Rebind devices.
> >>> echo 0000:00:14.0 >| /sys/bus/pci/drivers/xhci_hcd/bind
> >>> echo 0000:00:02.0 >| /sys/bus/pci/drivers/i915/bind
> > 
> >> ... you may still want to try replacing these with
> >> "xl pci-assignable-add ..." / "xl pci-assignable-remove ...".
> > 
> > We tested using the 'xl pci-assignable-add/remove' sequences and we
> > believe this may have resulted in the proper return of the devices to
> > dom0 but haven't been able to verify that since the Windows VM is now
> > throwing the VIDEO_TDR error.
> > 
> > Unless we are misunderstanding something the 'xl
> > pci-assignable-remove' sequence requires the manual re-binding of the
> > devices to their dom0 drivers.

> Hmm, I thought drivers would be rebound, but I'm not a tool stack
> person.  Looking at libxl__device_pci_assignable_remove() at least
> support this assumption of mine. You did use the command's -r
> option, didn't you?

No we weren't and I now see the -r option.

We have already re-worked our setup scripts to use pci-assignable-add
and will verify the -r option works as advertised, thanks for the tip.

We had our lab machine broken for a couple of days where it wouldn't
start an IGD pass-through session in any way shape or form.  We got
that sorted out and will now go back to 4.15.2 and verify what works
and doesn't work and report back.

> Jan

Have a good weekend.

As always,
Dr. G.W. Wettstein, Ph.D.   Enjellic Systems Development, LLC.
4206 N. 19th Ave.           Specializing in information infra-structure
Fargo, ND  58102            development.
PH: 701-281-1686            EMAIL: greg@enjellic.com
------------------------------------------------------------------------------
"On the other hand, the Linux philosophy is 'laugh in the face of
 danger'.  Oops.  Wrong one.  'Do it yourself'.  Thats it."
                                -- Linus Torvalds


  reply	other threads:[~2022-02-25  0:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-14  6:00 IGD pass-through failures since 4.10 Dr. Greg
2022-02-14  8:56 ` Jan Beulich
2022-02-17 20:15   ` Dr. Greg
2022-02-18  7:04     ` Jan Beulich
2022-02-22 18:52       ` Dr. Greg
2022-02-23  8:59         ` Jan Beulich
2022-02-25  0:16           ` Dr. Greg [this message]
2022-02-14  9:21 ` Roger Pau Monné
2022-02-18 23:12   ` Dr. Greg

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=20220225001602.GB5755@wind.enjellic.com \
    --to=greg@enjellic.com \
    --cc=jbeulich@suse.com \
    --cc=xen-devel@lists.xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.