All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dr. Greg" <greg@enjellic.com>
To: Roger Pau Monn?? <roger.pau@citrix.com>
Cc: xen-devel@lists.xen.org
Subject: Re: IGD pass-through failures since 4.10.
Date: Fri, 18 Feb 2022 17:12:42 -0600	[thread overview]
Message-ID: <20220218231242.GA6668@wind.enjellic.com> (raw)
In-Reply-To: <Ygoe/e+UzAtHe3Ac@Air-de-Roger>

On Mon, Feb 14, 2022 at 10:21:01AM +0100, Roger Pau Monn?? wrote:

Good afternoon, I hope the week has gone well for everyone.

> On Mon, Feb 14, 2022 at 12:00:11AM -0600, Dr. Greg wrote:

> >
> > [ Material removed ]
> >
> > It appears to be a problem with mapping interrupts back to dom0 given
> > that we see the following:
> > 
> > Feb 10 08:16:05 hostname kernel: xhci_hcd 0000:00:14.0: xen map irq failed -19 for 32752 domain
> > 
> > Feb 10 08:16:05 hostname kernel: i915 0000:00:02.0: xen map irq failed -19 for 32752 domain
> > 
> > Feb 10 08:16:12 hostname kernel: xhci_hcd 0000:00:14.0: Error while assigning device slot ID

> Are you testing with an hypervisor with debug enabled? If not,
> please build one and see if there are any messages in Xen dmesg also
> as a result of the error (uisng `xl dmesg` if you don't have a
> serial attached to the box). Posting full Linux and Xen dmesgs (Xen
> build with debug=y) could also help.

It was just a stock build out of the GIT tree.

We will get a debug hypervisors built and get traces out of the test
machine and post them to this thread.  I don't believe that dom0
kernel was talking very much about what was going on but we will
verify that.

> PHYSDEVOP_map_pirq is failing but without further information it's
> impossible to limit the scope of the issue (and whether the issue is
> with PHYSDEVOP_map_pirq or some previous operation).

Very useful piece of information to have.

From the log messages above, I assume the kernel is getting ENODEV
from the hypervisor call.  We will see if we can get some targeted
debug statements into the hypervisor to figure out what is going on.

> Thanks, Roger.

Thank you for the follow-up, have a good weekend.

Dr. Greg

As always,
Dr. Greg Wettstein, Ph.D    Worker / Principal Engineer
IDfusion, LLC
4206 19th Ave N.            Specialists in SGX secured infrastructure.
Fargo, ND  58102
PH: 701-281-1686            CELL: 701-361-2319
EMAIL: gw@idfusion.org
------------------------------------------------------------------------------
"Real Programmers consider "what you see is what you get" to be just as
 bad a concept in Text Editors as it is in women.  No, the Real
 Programmer wants a "you asked for it, you got it" text editor --
 complicated, cryptic, powerful, unforgiving, dangerous."
                                -- Matthias Schniedermeyer


      reply	other threads:[~2022-02-18 23:13 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
2022-02-14  9:21 ` Roger Pau Monné
2022-02-18 23:12   ` Dr. Greg [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=20220218231242.GA6668@wind.enjellic.com \
    --to=greg@enjellic.com \
    --cc=roger.pau@citrix.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.