From: Paolo Bonzini <pbonzini@redhat.com>
To: Jason Wang <jasowang@redhat.com>,
"Tian, Kevin" <kevin.tian@intel.com>,
"Zhao, Yan Y" <yan.y.zhao@intel.com>
Cc: 'Alex Williamson' <alex.williamson@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] vhost, iova, and dirty page tracking
Date: Thu, 19 Sep 2019 14:45:54 +0200 [thread overview]
Message-ID: <8fb74d6c-5449-bccb-deab-5300f2a50122@redhat.com> (raw)
In-Reply-To: <00084b36-3281-7c8d-5057-427eaabfb174@redhat.com>
On 19/09/19 14:39, Jason Wang wrote:
>> In general, userspace cannot assume that it's okay to sync just through
>> GPA1. It must sync the host page if *either* GPA1 or GPA2 are marked
>> dirty.
>
> Maybe we need document this somewhere.
Well, it's implicit but it should be kind of obvious. The dirty page
only tells you that the guest wrote to the GPA, HVAs are never mentioned
in the documentation.
Paolo
> Any other issue that still need to be covered consider userspace need to
> sync both GPAs?
>
> Thanks
>
next prev parent reply other threads:[~2019-09-19 12:52 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-16 1:51 [Qemu-devel] vhost, iova, and dirty page tracking Tian, Kevin
2019-09-16 8:33 ` Jason Wang
2019-09-17 8:48 ` Tian, Kevin
2019-09-17 10:36 ` Jason Wang
2019-09-18 1:44 ` Tian, Kevin
2019-09-18 6:10 ` Jason Wang
2019-09-18 7:41 ` Tian, Kevin
2019-09-18 8:37 ` Tian, Kevin
2019-09-19 1:05 ` Jason Wang
2019-09-19 5:28 ` Yan Zhao
2019-09-19 6:09 ` Jason Wang
2019-09-19 6:17 ` Yan Zhao
2019-09-19 6:32 ` Jason Wang
2019-09-19 6:29 ` Yan Zhao
2019-09-19 6:32 ` Yan Zhao
2019-09-19 9:35 ` Jason Wang
2019-09-19 9:36 ` Yan Zhao
2019-09-19 10:08 ` Jason Wang
2019-09-19 10:06 ` Jason Wang
2019-09-19 10:16 ` Yan Zhao
2019-09-19 12:14 ` Jason Wang
2019-09-19 7:16 ` Tian, Kevin
2019-09-19 9:37 ` Jason Wang
2019-09-19 14:06 ` Michael S. Tsirkin
2019-09-20 1:15 ` Jason Wang
2019-09-20 10:02 ` Michael S. Tsirkin
2019-09-19 11:14 ` Paolo Bonzini
2019-09-19 12:39 ` Jason Wang
2019-09-19 12:45 ` Paolo Bonzini [this message]
2019-09-19 22:54 ` Tian, Kevin
2019-09-20 1:18 ` Jason Wang
2019-09-24 2:02 ` Tian, Kevin
2019-09-25 3:46 ` Jason Wang
2019-09-17 14:54 ` Alex Williamson
2019-09-18 1:31 ` Tian, Kevin
2019-09-18 6:03 ` Jason Wang
2019-09-18 7:21 ` Tian, Kevin
2019-09-19 17:20 ` Alex Williamson
2019-09-19 22:40 ` Tian, Kevin
[not found] ` <AADFC41AFE54684AB9EE6CBC0274A5D19D57AFB7@SHSMSX104.ccr.corp.intel.com>
2019-09-18 2:15 ` Tian, Kevin
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=8fb74d6c-5449-bccb-deab-5300f2a50122@redhat.com \
--to=pbonzini@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=jasowang@redhat.com \
--cc=kevin.tian@intel.com \
--cc=qemu-devel@nongnu.org \
--cc=yan.y.zhao@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.