Re: [Xen-devel] [PATCH V8 00/12] xen: Clean-up of mem_event subsystem

[Tamas Lengyel <tamas.lengyel@xxxxxxxxxxxx>]

On Thu, Apr 9, 2015 at 1:07 PM, Tamas Lengyel <tamas.lengyel@xxxxxxxxxxxx> wrote:

On Thu, Apr 9, 2015 at 1:03 PM, Tim Deegan <tim@xxxxxxx> wrote:

Hi,

Sorry for the delay - I have been away.

At 22:06 +0100 on 26 Mar (1427407612), Tamas K Lengyel wrote:
> Tamas K Lengyel (12):
>Â Âxen/mem_event: Cleanup of mem_event structures
>Â Âxen/mem_event: Cleanup mem_event names in rings, functions and domctls
>Â Âxen/mem_paging: Convert mem_event_op to mem_paging_op and cleanup
>Â Âxen: Rename mem_event to vm_event
>Â Âtools/tests: Clean-up tools/tests/xen-access
>Â Âx86/hvm: factor out and rename vm_event related functions

I have applied these six patches.

>Â Âxen: Introduce monitor_op domctl

This one no longer applies cleanly - looks like a conflict with a7511905
("xen: Extend DOMCTL createdomain to support arch configuration")

Can you rebase the second half of the series please?

Absolutely. Will be sending it shortly, thanks.

Tamas

Â

Cheers,

Tim.

What's the policy on reusing DOMCTL numbers? I see XEN_DOMCTL_arm_configure_domain has been retired in the conflicting patch. Should I just reuse it's number for monitor_op? For the most part domctl numbers seem to be continuous but there are holes (30-32) so I'm not sure.

Tamas

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