Re: [Xen-devel] [PATCH for-4.5 v8 12/19] xen/arm: p2m changes for mem_access support

[Razvan Cojocaru <rcojocaru@xxxxxxxxxxxxxxx>]

On 09/24/14 19:58, Tamas K Lengyel wrote:
> 
> 
> On Wed, Sep 24, 2014 at 4:40 PM, Ian Campbell <Ian.Campbell@xxxxxxxxxx
> <mailto:Ian.Campbell@xxxxxxxxxx>> wrote:
> 
>     On Tue, 2014-09-23 at 15:14 +0200, Tamas K Lengyel wrote:
>     > Add p2m_access_t to struct page_info and add necessary changes for
>     > page table construction routines to pass the default access information.
>     > We store the p2m_access_t info in page_info as the PTE lacks enough
>     > software programmable bits.
> 
>     The last bit of this is now out of date.
> 
> 
> Ack.
>  
> 
> 
>     > diff --git a/xen/include/asm-arm/domain.h b/xen/include/asm-arm/domain.h
>     > index 787e93c..3d69152 100644
>     > --- a/xen/include/asm-arm/domain.h
>     > +++ b/xen/include/asm-arm/domain.h
>     > @@ -17,6 +17,7 @@ struct hvm_domain
>     >  {
>     >      uint64_t              params[HVM_NR_PARAMS];
>     >      struct hvm_iommu      iommu;
>     > +    bool_t                introspection_enabled;
> 
>     I've not found the user of this yet, but is it not somewhat redundant
>     with p2m->access_in_use?
> 
> 
> It's used by mem_event memop for XEN_DOMCTL_MEM_EVENT_OP_ACCESS_DISABLE.
> I just added this one field to the hvm_domain for compat reasons instead
> of abstracting setting that value to 0 and adding an empty inline for
> ARM. This looked like less trouble.

Indeed, that's used (at the moment) to make sure x86 MSR write
interception doesn't get disabled for memory introspection clients. I
guess on ARM it is less useful now, but since hopefully ARM development
of this feature will happen at some point in the future, it would
explain Tamas' choice.


Regards,
Razvan Cojocaru

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