From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Tamas K Lengyel <tamas.lengyel@zentific.com>, xen-devel@lists.xen.org
Cc: kevin.tian@intel.com, wei.liu2@citrix.com,
ian.campbell@citrix.com, stefano.stabellini@eu.citrix.com,
ian.jackson@eu.citrix.com, tim@xen.org, jbeulich@suse.com,
eddie.dong@intel.com, andres@lagarcavilla.org,
jun.nakajima@intel.com, rshriram@cs.ubc.ca, keir@xen.org,
dgdegra@tycho.nsa.gov, yanghy@cn.fujitsu.com
Subject: Re: [RFC PATCH V2 0/8] xen: Clean-up of mem_event subsystem
Date: Mon, 19 Jan 2015 13:03:35 +0000 [thread overview]
Message-ID: <54BD00A7.1000804@citrix.com> (raw)
In-Reply-To: <1421594281-27658-1-git-send-email-tamas.lengyel@zentific.com>
On 18/01/15 15:17, Tamas K Lengyel wrote:
> This patch series aims to clean up the mem_event subsystem within Xen. The
> original use-case for this system was to allow external helper applications
> running in privileged domains to control various memory operations performed
> by Xen. Amongs these were paging, sharing and access control. The subsystem
> has since been extended to also deliver non-memory related events, namely
> various HVM debugging events (INT3, MTF, MOV-TO-CR, MOV-TO-MSR). The structures
> and naming of related functions however has not caught up to these new
> use-cases, thus leaving many ambigouities in the code.
>
> In this series we convert the mem_event structures to a union of sub-structures
> which clearly define the scope of information that is transmitted via the event
> delivery mechanism. Afterwards, we clean up the naming of the structures and
> related functions to more clearly be in line with their actual operations.
>
> This RFC PATCH series is also available at:
> https://github.com/tklengyel/xen/tree/mem_event_cleanup2
One note to start with. There are a lot of file renames in this
series. Using gits -M option for patches should make the series rather
smaller.
I also wonder whether it might be easier to organise the series along
the lines of introducing vm_event, move the existing interfaces across,
then deleting mem_event. Lets see how easy it is to review in its
current form first though.
~Andrew
next prev parent reply other threads:[~2015-01-19 13:03 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-18 15:17 [RFC PATCH V2 0/8] xen: Clean-up of mem_event subsystem Tamas K Lengyel
2015-01-18 15:17 ` [RFC PATCH V2 1/8] xen/mem_event: Cleanup of mem_event structures Tamas K Lengyel
2015-01-22 12:43 ` Tim Deegan
2015-01-22 12:50 ` Razvan Cojocaru
2015-01-22 12:50 ` Tamas K Lengyel
2015-01-22 12:53 ` Razvan Cojocaru
2015-01-22 13:11 ` Tim Deegan
2015-01-22 15:00 ` Jan Beulich
2015-01-22 15:34 ` Tamas K Lengyel
2015-01-22 16:00 ` Jan Beulich
2015-01-22 16:23 ` Tamas K Lengyel
2015-01-22 16:34 ` Jan Beulich
[not found] ` <CAErYnsj8B1Fbo=JD3hLz-8kjtt-FoWTrSkGnbkvVf=iR64MDBQ@mail.gmail.com>
2015-01-23 9:00 ` Jan Beulich
2015-01-23 9:18 ` Tamas K Lengyel
2015-01-29 11:54 ` Tamas K Lengyel
2015-01-29 12:02 ` Jan Beulich
2015-01-29 12:09 ` Tamas K Lengyel
2015-01-29 12:15 ` Tamas K Lengyel
2015-01-29 12:51 ` Jan Beulich
2015-01-29 13:03 ` Tamas K Lengyel
2015-01-18 15:17 ` [RFC PATCH V2 2/8] xen/mem_event: Rename the mem_event ring from 'access' to 'monitor' Tamas K Lengyel
2015-01-22 12:53 ` Tim Deegan
2015-01-22 14:12 ` Tamas K Lengyel
2015-01-22 15:02 ` Jan Beulich
2015-01-22 15:42 ` Tamas K Lengyel
2015-01-18 15:17 ` [RFC PATCH V2 3/8] xen/mem_paging: Convert mem_event_op to mem_paging_op Tamas K Lengyel
2015-01-22 13:03 ` Tim Deegan
2015-01-22 15:09 ` Jan Beulich
2015-01-22 15:41 ` Tamas K Lengyel
2015-01-18 15:17 ` [RFC PATCH V2 4/8] x86/hvm: rename hvm_memory_event_* functions to hvm_event_* Tamas K Lengyel
2015-01-22 13:05 ` Tim Deegan
2015-01-22 15:56 ` Andrew Cooper
2015-01-22 16:34 ` Tamas K Lengyel
2015-01-18 15:17 ` [RFC PATCH V2 5/8] xen/mem_event: Rename mem_event to vm_event Tamas K Lengyel
2015-01-22 14:52 ` Tim Deegan
2015-01-22 15:02 ` Tamas K Lengyel
2015-01-18 15:17 ` [RFC PATCH V2 6/8] xen/vm_event: Decouple vm_event and mem_access Tamas K Lengyel
2015-01-22 14:56 ` Tim Deegan
2015-01-22 15:35 ` Tamas K Lengyel
2015-01-18 15:18 ` [RFC PATCH V2 7/8] tools/tests: Clean-up tools/tests/xen-access Tamas K Lengyel
2015-01-18 15:18 ` [RFC PATCH V2 8/8] x86/hvm: factor out vm_event related functions into separate file Tamas K Lengyel
2015-01-22 15:00 ` Tim Deegan
2015-01-22 15:36 ` Tamas K Lengyel
2015-01-22 16:25 ` Jan Beulich
2015-01-22 16:42 ` Tamas K Lengyel
2015-01-22 16:50 ` Tim Deegan
2015-01-23 8:56 ` Razvan Cojocaru
2015-01-23 9:03 ` Jan Beulich
2015-01-23 9:21 ` Tamas K Lengyel
2015-01-22 16:32 ` Andrew Cooper
2015-01-22 16:41 ` Tamas K Lengyel
2015-01-19 13:03 ` Andrew Cooper [this message]
2015-01-21 10:59 ` [RFC PATCH V2 0/8] xen: Clean-up of mem_event subsystem Tamas K Lengyel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54BD00A7.1000804@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=andres@lagarcavilla.org \
--cc=dgdegra@tycho.nsa.gov \
--cc=eddie.dong@intel.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=jun.nakajima@intel.com \
--cc=keir@xen.org \
--cc=kevin.tian@intel.com \
--cc=rshriram@cs.ubc.ca \
--cc=stefano.stabellini@eu.citrix.com \
--cc=tamas.lengyel@zentific.com \
--cc=tim@xen.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.org \
--cc=yanghy@cn.fujitsu.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.