* Question about xc_translate_foreign_address()
@ 2011-05-25 4:47 AP Xen
2011-05-25 6:16 ` Keir Fraser
0 siblings, 1 reply; 2+ messages in thread
From: AP Xen @ 2011-05-25 4:47 UTC (permalink / raw)
To: xen-devel
I have a question about xc_translate_foreign_address(). When this call
is issued for VCPU1 in a 2 VCPU guest where VCPU1 is in a paused state
and VCPU0 is active, there is a possibility that VCPU0 could change
the page tables that VCPU1 is using. There is a window where the
function could return incorrect information. Is this true or there is
something that prevents it from happening?
Thanks,
AP
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Question about xc_translate_foreign_address()
2011-05-25 4:47 Question about xc_translate_foreign_address() AP Xen
@ 2011-05-25 6:16 ` Keir Fraser
0 siblings, 0 replies; 2+ messages in thread
From: Keir Fraser @ 2011-05-25 6:16 UTC (permalink / raw)
To: AP Xen, xen-devel
On 25/05/2011 05:47, "AP Xen" <apxeng@gmail.com> wrote:
> I have a question about xc_translate_foreign_address(). When this call
> is issued for VCPU1 in a 2 VCPU guest where VCPU1 is in a paused state
> and VCPU0 is active, there is a possibility that VCPU0 could change
> the page tables that VCPU1 is using. There is a window where the
> function could return incorrect information. Is this true or there is
> something that prevents it from happening?
The assumption is that the whole domain is paused.
-- Keir
> Thanks,
> AP
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2011-05-25 6:16 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-05-25 4:47 Question about xc_translate_foreign_address() AP Xen
2011-05-25 6:16 ` Keir Fraser
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).