From: Greg KH <gregkh@linuxfoundation.org>
To: "James D. Turner" <linuxkernel.foss@dmarc-none.turner.link>
Cc: Alex Williamson <alex.williamson@redhat.com>,
kvm@vger.kernel.org, regressions@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [REGRESSION] Too-low frequency limit for AMD GPU PCI-passed-through to Windows VM
Date: Mon, 17 Jan 2022 09:09:07 +0100 [thread overview]
Message-ID: <YeUkIyAsrYHOuaKt@kroah.com> (raw)
In-Reply-To: <87ee57c8fu.fsf@turner.link>
On Sun, Jan 16, 2022 at 09:12:21PM -0500, James D. Turner wrote:
> So, the issue was introduced between v5.13 and v5.14-rc1. I'm willing to
> bisect the commit history to narrow it down further, if that would be
> helpful.
Bisection would be great as that is a very large range of commits there
from many months ago, so people might not remember what could have
caused this issue.
thanks,
greg k-h
next parent reply other threads:[~2022-01-17 8:09 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87ee57c8fu.fsf@turner.link>
2022-01-17 8:09 ` Greg KH [this message]
2022-01-17 9:03 ` Thorsten Leemhuis
2022-01-18 3:14 ` James Turner
2022-01-21 2:13 ` James Turner
2022-01-21 6:22 ` Thorsten Leemhuis
2022-01-21 16:45 ` Alex Deucher
2022-01-22 0:51 ` James Turner
2022-01-22 5:52 ` Lazar, Lijo
2022-01-22 21:11 ` James Turner
2022-01-24 14:21 ` Lazar, Lijo
2022-01-24 23:58 ` James Turner
2022-01-25 13:33 ` Lazar, Lijo
2022-01-30 0:25 ` Jim Turner
2022-02-15 14:56 ` Thorsten Leemhuis
2022-02-15 15:11 ` Alex Deucher
[not found] ` <87pmnnpmh5.fsf@dmarc-none.turner.link>
2022-02-16 16:37 ` Alex Deucher
2022-03-06 15:48 ` Thorsten Leemhuis
2022-03-07 2:12 ` James Turner
2022-03-13 18:33 ` James Turner
2022-03-17 12:54 ` Thorsten Leemhuis
2022-03-18 5:43 ` Paul Menzel
2022-03-18 7:01 ` Thorsten Leemhuis
2022-03-18 14:46 ` Alex Williamson
2022-03-18 15:06 ` Alex Deucher
2022-03-18 15:25 ` Alex Williamson
2022-03-21 1:26 ` James Turner
2022-01-24 17:04 ` Alex Deucher
2022-01-24 17:30 ` Alex Williamson
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=YeUkIyAsrYHOuaKt@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=alex.williamson@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxkernel.foss@dmarc-none.turner.link \
--cc=regressions@lists.linux.dev \
/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
Powered by JetHome