From: Igor Druzhinin <igor.druzhinin@citrix.com>
To: Anthony PERARD <anthony.perard@citrix.com>
Cc: xen-devel@lists.xenproject.org, qemu-devel@nongnu.org,
sstabellini@kernel.org, ross.lagerwall@citrix.com
Subject: Re: [Qemu-devel] [PATCH] xen/pt: use address_space_memory object for memory region hooks
Date: Tue, 17 Apr 2018 15:29:42 +0100 [thread overview]
Message-ID: <c7d408cb-454c-2322-3812-a7cacecdbe5f@citrix.com> (raw)
In-Reply-To: <20180417141518.GM2208@perard>
On 17/04/18 15:15, Anthony PERARD wrote:
> On Fri, Apr 06, 2018 at 10:21:23PM +0100, Igor Druzhinin wrote:
>> Commit 99605175c (xen-pt: Fix PCI devices re-attach failed) introduced
>> a subtle bug. As soon as the guest switches off Bus Mastering on the
>> device it immediately causes all the BARs be unmapped due to the DMA
>> address space of the device being changed. This is undesired behavior
>> because the guest may try to communicate with the device after that
>> which triggers the following errors in the logs:
>>
>> [00:05.0] xen_pt_bar_read: Error: Should not read BAR through QEMU. @0x0000000000000200
>> [00:05.0] xen_pt_bar_write: Error: Should not write BAR through QEMU. @0x0000000000000200
>>
>> The issue that the original patch tried to workaround (uneven number of
>> region_add/del calls on device attach/detach) was fixed in later QEMU
>> versions.
>
> Do you know when the issue was fixed?
>
I think it's this commit:
commit d25836cafd7508090d211e97acfc0abc5ae88daa
Author: Peter Xu <peterx@redhat.com>
Date: Mon Jan 22 14:02:44 2018 +0800
memory: do explicit cleanup when remove listeners
Igor
prev parent reply other threads:[~2018-04-17 14:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-06 21:21 [Qemu-devel] [PATCH] xen/pt: use address_space_memory object for memory region hooks Igor Druzhinin
2018-04-17 13:58 ` Igor Druzhinin
2018-04-17 14:15 ` Anthony PERARD
2018-04-17 14:18 ` Igor Druzhinin
2018-04-17 14:37 ` Anthony PERARD
2018-04-17 14:29 ` Igor Druzhinin [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=c7d408cb-454c-2322-3812-a7cacecdbe5f@citrix.com \
--to=igor.druzhinin@citrix.com \
--cc=anthony.perard@citrix.com \
--cc=qemu-devel@nongnu.org \
--cc=ross.lagerwall@citrix.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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).