[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] about the funtion call memory_type_changed()

>>> On 22.01.15 at 08:44, <yang.z.zhang@xxxxxxxxx> wrote:
> Tian, Kevin wrote on 2015-01-22:
>>> From: Jan Beulich [mailto:JBeulich@xxxxxxxx]
>>> Sent: Wednesday, January 21, 2015 6:31 PM
>>>> Yes, it's true. But I still don't understand why to do the
>>>> flush_all just when iommu_enable is true. Could you  explain why ?
>>> The question you raise doesn't reflect what the function does: It
>>> doesn't flush when iommu_enabled, in calls
>>> p2m_memory_type_changed() in that case. And that operation is what
>>> requires a flush afterwards (unless we know that nothing can be
>>> cached yet), as there may have been a cachable -> non- cachable
>>> transition for some of the pages assigned to the guest.
> I find in vmx_wbinvd_intercept(), it will check whether iommu_snoop is 
> enabled before flushing. And this check exists in memory_type_changes() 
> before, but it is removed by you. I think either both are removed or both are 
> there. Is there any difference between the two code pieces?

I had raised the question on the various uses of iommu_snoop quite
some time ago - afair without ever getting a satisfying answer. Some
(if not all) instances look suspicious, but without knowing all the
details I can't really propose a patch removing some/all of them.

>>> The fact that the call is made dependent on iommu_enabled is simply
>>> because when that flag is not set, all memory of the guest is
>>> treated WB (as no physical device can be assigned to the guest in
>>> that case), and hence to type changes can occur.
> Even the flush is required, the flush_all is too heavy. Just use the 
> vcpu_dirty_cpumask is enough.

No, that mask isn't sufficient - when a CPU gets cleared from it,
its cache doesn't get flushed (only the TLB would).


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.