From: "Cédric Le Goater" <clegoate@redhat.com>
To: Michael Tokarev <mjt@tls.msk.ru>,
Alex Williamson <alex.williamson@redhat.com>,
kraxel@redhat.com
Cc: "Marc-André Lureau" <marcandre.lureau@gmail.com>,
"Kim, Dongwon" <dongwon.kim@intel.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
qemu-devel@nongnu.org, "Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [PATCH for-8.1] vfio/display: Fix missing update to set backing fields
Date: Fri, 22 Sep 2023 13:10:07 +0200 [thread overview]
Message-ID: <8c13e55d-5894-d81d-23e7-5cd693093589@redhat.com> (raw)
In-Reply-To: <a95cb9f0-cdef-a0e9-c472-31f5534e58c1@tls.msk.ru>
On 9/22/23 11:49, Michael Tokarev wrote:
> 22.09.2023 12:38, Cédric Le Goater wrote:
>> On 9/13/23 21:18, Alex Williamson wrote:
>>>
>>> Hi Gerd,
>>>
>>> Some consultation would be appreciated on this thread to get this patch
>>> out of limbo. Is there a better solution that what I've proposed?
>>
>> This does fix a regression reproducible on systems with an Intel Gen 8,
>> my T480 laptop for instance.
>>
>> Tested-by: Cédric Le Goater <clg@redhat.com>
>>
>> Also, queuing it in vfio-next.
>>
>
> Is it not https://gitlab.com/qemu-project/qemu/-/issues/1891 ?
It is.
Resolves: https://gitlab.com/qemu-project/qemu/-/issues/1891
Thanks,
C.
next prev parent reply other threads:[~2023-09-22 11:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-16 21:55 [PATCH for-8.1] vfio/display: Fix missing update to set backing fields Alex Williamson
2023-08-16 22:31 ` Philippe Mathieu-Daudé
2023-08-17 16:28 ` Kim, Dongwon
2023-09-04 11:06 ` Marc-André Lureau
2023-09-04 14:11 ` Alex Williamson
2023-09-04 17:00 ` Marc-André Lureau
2023-09-05 15:09 ` Alex Williamson
2023-09-13 19:18 ` Alex Williamson
2023-09-22 9:38 ` Cédric Le Goater
2023-09-22 9:49 ` Michael Tokarev
2023-09-22 11:10 ` Cédric Le Goater [this message]
2023-10-03 17:03 ` Michael Tokarev
2023-10-03 21:17 ` Cédric Le Goater
-- strict thread matches above, loose matches on Subject: below --
2023-10-14 9:09 Edmund Raile
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=8c13e55d-5894-d81d-23e7-5cd693093589@redhat.com \
--to=clegoate@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=dongwon.kim@intel.com \
--cc=kraxel@redhat.com \
--cc=marcandre.lureau@gmail.com \
--cc=mjt@tls.msk.ru \
--cc=mst@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.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).