From: Andrew Cooper <andrew.cooper3@citrix.com>
To: xen-devel@lists.xen.org
Subject: Re: [PATCH V8 00/12] xen: Clean-up of mem_event subsystem
Date: Thu, 9 Apr 2015 12:21:18 +0100 [thread overview]
Message-ID: <552660AE.30400@citrix.com> (raw)
In-Reply-To: <CABfawhnvyPCC-Q0JK86nytN2--L_FQoXRgKG2XqyzaPO0_YivQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1871 bytes --]
On 09/04/15 12:15, Tamas Lengyel wrote:
>
>
> On Thu, Apr 9, 2015 at 1:07 PM, Tamas Lengyel
> <tamas.lengyel@zentific.com <mailto:tamas.lengyel@zentific.com>> wrote:
>
>
>
> On Thu, Apr 9, 2015 at 1:03 PM, Tim Deegan <tim@xen.org
> <mailto:tim@xen.org>> 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.
While technically speaking it would be fine to reuse, given the
INTERFACE_VERSION, it would be better to leave the holes as -ENOSYS to
positively catch potential issues. We have 32bits worth of domctl subop
space - we can afford to have a few holes ;)
~Andrew
[-- Attachment #1.2: Type: text/html, Size: 4963 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2015-04-09 11:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-26 21:06 [PATCH V8 00/12] xen: Clean-up of mem_event subsystem Tamas K Lengyel
2015-03-26 21:06 ` [PATCH V8 01/12] xen/mem_event: Cleanup of mem_event structures Tamas K Lengyel
2015-03-26 21:06 ` [PATCH V8 02/12] xen/mem_event: Cleanup mem_event names in rings, functions and domctls Tamas K Lengyel
2015-03-26 21:06 ` [PATCH V8 03/12] xen/mem_paging: Convert mem_event_op to mem_paging_op and cleanup Tamas K Lengyel
2015-03-26 21:06 ` [PATCH V8 04/12] xen: Rename mem_event to vm_event Tamas K Lengyel
2015-03-26 21:06 ` [PATCH V8 05/12] tools/tests: Clean-up tools/tests/xen-access Tamas K Lengyel
2015-03-26 21:06 ` [PATCH V8 06/12] x86/hvm: factor out and rename vm_event related functions Tamas K Lengyel
2015-03-26 21:06 ` [PATCH V8 07/12] xen: Introduce monitor_op domctl Tamas K Lengyel
2015-03-27 10:20 ` Jan Beulich
2015-03-26 21:07 ` [PATCH V8 08/12] xen/vm_event: Deprecate VM_EVENT_FLAG_DUMMY flag Tamas K Lengyel
2015-03-26 21:07 ` [PATCH V8 09/12] xen/vm_event: Decouple vm_event and mem_access Tamas K Lengyel
2015-03-26 21:07 ` [PATCH V8 10/12] xen/vm_event: Relocate memop checks Tamas K Lengyel
2015-03-26 21:07 ` [PATCH V8 11/12] xen/xsm: Split vm_event_op into three separate labels Tamas K Lengyel
2015-03-26 21:07 ` [PATCH V8 12/12] xen/vm_event: Add RESUME option to vm_event_op domctl Tamas K Lengyel
2015-04-09 11:03 ` [PATCH V8 00/12] xen: Clean-up of mem_event subsystem Tim Deegan
2015-04-09 11:07 ` Tamas Lengyel
2015-04-09 11:15 ` Tamas Lengyel
2015-04-09 11:21 ` Andrew Cooper [this message]
2015-04-09 11:30 ` Tim Deegan
2015-04-14 11:31 ` Ian Campbell
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=552660AE.30400@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=xen-devel@lists.xen.org \
/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.