From: AL13N <alien@rmail.be>
To: Xen-devel <xen-devel@lists.xen.org>
Cc: Jan Beulich <jbeulich@suse.com>
Subject: Re: pci passthrough issue introduced between 4.14.1 and 4.15.0
Date: Tue, 01 Jun 2021 16:06:28 +0200 [thread overview]
Message-ID: <a7c0e9b0cdd8f9e709abc329c7f6239c@mail.rmail.be> (raw)
In-Reply-To: <e9a3f7a8-7bf2-4f0a-cc25-d8ce015df1f2@suse.com>
Jan Beulich schreef op 2021-06-01 12:08:
> On 01.06.2021 09:36, AL13N wrote:
>> Not 100% it's a bug or something i did wrong, but,
>>
>> with xl create i start a PV with 3 pci passthroughs
>>
>> after wards, xl pci-list shows all 3 nicely
>>
>> looking at the domU boot logs, pcifront is only creating one pci
>> device
>> and lspci in the guest shows only 1 pci entry
>>
>> in at least 4.14.1 it still works.
>
> This reminds me of my report at
> https://lists.xen.org/archives/html/xen-devel/2021-03/msg00956.html
>
> Meanwhile the proposed pciback change has gone in upstream:
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/xen/xen-pciback?id=c81d3d24602540f65256f98831d0a25599ea6b87
>
> I wasn't, however, aware that this may have been an issue going
> from 4.14.1 to 4.15.0, i.e. something that was presumably (as
> George also has just said) a regression in the tools. Or else I
> probably wouldn't have suggested taking care of this in Linux.
> Nevertheless you may want to give that change a try.
Well, both tests have only different tools en hypervisor, no kernel was
changed between both tests, neither in dom0 or domU , so, it might not
be pciback?
next prev parent reply other threads:[~2021-06-01 14:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-01 7:36 pci passthrough issue introduced between 4.14.1 and 4.15.0 AL13N
2021-06-01 10:08 ` Jan Beulich
2021-06-01 14:06 ` AL13N [this message]
2021-06-01 14:28 ` AL13N
2021-06-01 14:33 ` Jan Beulich
2021-06-01 14:44 ` AL13N
2021-06-01 14:48 ` AL13N
2021-06-01 15:50 ` AL13N
2021-06-01 14:53 ` Jan Beulich
2021-06-03 16:01 ` AL13N
2021-06-04 6:56 ` Jan Beulich
2021-06-04 7:10 ` Juergen Gross
2021-06-04 8:37 ` AL13N
-- strict thread matches above, loose matches on Subject: below --
2021-06-01 7:34 AL13N
2021-06-01 10:03 ` George Dunlap
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=a7c0e9b0cdd8f9e709abc329c7f6239c@mail.rmail.be \
--to=alien@rmail.be \
--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 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).