From: Jan Beulich <jbeulich@suse.com>
To: AL13N <alien@rmail.be>
Cc: Xen-devel <xen-devel@lists.xen.org>
Subject: Re: pci passthrough issue introduced between 4.14.1 and 4.15.0
Date: Fri, 4 Jun 2021 08:56:03 +0200 [thread overview]
Message-ID: <8a572357-e743-80a6-fed6-3c4999b986ec@suse.com> (raw)
In-Reply-To: <0100caba62175123c63f0df4749a8c88@mail.rmail.be>
On 03.06.2021 18:01, AL13N wrote:
> Jan Beulich schreef op 2021-06-01 16:53:
>> On 01.06.2021 16:44, AL13N wrote:
>>> This mailing list is the correct place for the toolstack too? right?
>>
>> Yes.
>
> So, what's the plan to fix this? is the plan to fix the toolstack? or
> put your patch in kernel to kinda workaround it?
The patch has already been put in the kernel, as said. It would be good
to know whether it actually has helped your case as well.
> Is there a way to make a regression test or unit test or something?
Would be nice, but may be a little difficult to arrange for in, say,
osstest.
> Does anyone have an idea on what patch would cause the regression?
Not me, but I'm also not a tool stack maintainer (nor expert in any
way).
Jan
> that
> patch that I pointed out, could it be that one, or should i look at a
> specific file/line? I can't really just test all of the patches and/or
> combinations. I'm not really at home with the xen code; and my single
> xen server is production, so i can really only test in weekends...
>
> AL13N
>
next prev parent reply other threads:[~2021-06-04 6:56 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
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 [this message]
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=8a572357-e743-80a6-fed6-3c4999b986ec@suse.com \
--to=jbeulich@suse.com \
--cc=alien@rmail.be \
--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).