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

Re: [Xen-devel] question about ept_set_entry


  • To: Jan Beulich <JBeulich@xxxxxxxx>
  • From: "Zhang, Chunyu" <zhangcy@xxxxxxxxxxxxxx>
  • Date: Fri, 29 Apr 2016 09:27:11 +0000
  • Accept-language: zh-CN, en-US
  • Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Fri, 29 Apr 2016 09:27:23 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xen.org>
  • Thread-index: AQHRoflOE6dnW7A4JUKFbhbRi9O1DQ==
  • Thread-topic: Re: [Xen-devel] question about ept_set_entry

hi jan
>>>> On 29.04.16 at 11:14, <zhangcy@xxxxxxxxxxxxxx> wrote:
>> hi all
>> 
>> in
>> - p2m-ept.c
>>   - ept_set_entry
>> 
>> i see code about iommu,
>> those code  for what?
>
>For keeping the IOMMU translation tables in sync with the CPU ones?
got it, thanks.
i will check IOMMU translation.
>But perhaps I'm simply not understanding what you try to get at...
i only want to know the  purpose of those code.
>
>Jan
>
>> -----
>> 
>>     if ( rc == 0 && p2m_is_hostp2m(p2m) && need_iommu(d) &&
>>          need_modify_vtd_table )
>>     {
>>         if ( iommu_hap_pt_share )
>>             iommu_pte_flush(d, gfn, &ept_entry->epte, order, 
>> vtd_pte_present);
>>         else
>>         {
>>             if ( iommu_flags )
>>                 for ( i = 0; i < (1 << order); i++ )
>>                     iommu_map_page(d, gfn + i, mfn_x(mfn) + i, iommu_flags);
>>             else
>>                 for ( i = 0; i < (1 << order); i++ )
>>                     iommu_unmap_page(d, gfn + i);
>>         }
>>     }
>> 
>> 
>> --------------
>> --------------
>> A new email address of FJWAN is launched from Apr.1 2007.
>> The updated address is: zhangcy@xxxxxxxxxxxxxx 
>> --------------------------------------------------
>> Zhang Chunyu
>> Nanjing Fujitsu Nanda Software Tech. Co., Ltd.(FNST)
>> No. 6 Wenzhu Road, Nanjing, 210012, China
>> TEL:+86+25-86630566-9566
>> FUJITSU INTERNAL:7998-9566
>> FAX:+86+25-83317685
>> EMail:zhangcy@xxxxxxxxxxxxxx 
>> --------------------------------------------------
>> This communication is for use by the intended recipient(s) only and may 
>> contain information that is privileged, confidential and exempt from 
>> disclosure under applicable law. If you are not an intended recipient of 
>> this 
>> communication, you are hereby notified that any dissemination, distribution 
>> or copying hereof is strictly prohibited.  If you have received this 
>> communication in error, please notify me by reply e-mail, permanently delete 
>> this communication from your system, and destroy any hard copies you may 
>> have 
>> printed.
>> 
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@xxxxxxxxxxxxx 
>> http://lists.xen.org/xen-devel 
>
>
>
>

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel

 


Rackspace

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