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

Re: [Xen-devel] [PATCH RFC 1/2] x86/mem_access: Make the mem_access ops generic

To: "Aravindh Puthiyaparambil (aravindp)" <aravindp@xxxxxxxxx>
From: "Jan Beulich" <JBeulich@xxxxxxxx>
Date: Thu, 10 Apr 2014 07:17:00 +0100
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxxx>, KeirFraser <keir@xxxxxxx>, Tim Deegan <tim@xxxxxxx>
Delivery-date: Thu, 10 Apr 2014 06:17:12 +0000
List-id: Xen developer discussion <xen-devel.lists.xen.org>

>>> On 10.04.14 at 02:39, <aravindp@xxxxxxxxx> wrote:
>>Also I don't see the need for the xenmem_ prefix.
> 
> I will get rid of the prefix. What about the enum? Should I call it 
> mem_access_t and MEM_access_*?

Definitely not - everything (new; I know we have things violating this)
in global name space should have a XEN, xen, XEN_, or xen_ prefix.

Jan


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

References:
- [Xen-devel] [PATCH RFC 0/2] Make mem_access APIs and hypercalls generic
  - From: Aravindh Puthiyaparambil
- [Xen-devel] [PATCH RFC 1/2] x86/mem_access: Make the mem_access ops generic
  - From: Aravindh Puthiyaparambil
- Re: [Xen-devel] [PATCH RFC 1/2] x86/mem_access: Make the mem_access ops generic
  - From: Jan Beulich
- Re: [Xen-devel] [PATCH RFC 1/2] x86/mem_access: Make the mem_access ops generic
  - From: Aravindh Puthiyaparambil (aravindp)

Prev by Date: Re: [Xen-devel] [RFC PATCH] page_alloc: use first half of higher order chunks when halving
Next by Date: [Xen-devel] BUG: unable to handle kernel paging request
Previous by thread: Re: [Xen-devel] [PATCH RFC 1/2] x86/mem_access: Make the mem_access ops generic
Next by thread: [Xen-devel] [PATCH] tools/hotplug: Remove network-*
Index(es):
- Date
- Thread

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