> -----Original Message----- > From: Andrii Anisov [mailto:andrii.ani...@gmail.com] > Sent: 16 February 2017 12:03 > To: xen-de...@lists.xenproject.org > Cc: andrii_ani...@epam.com; Andrew Cooper > <andrew.coop...@citrix.com>; George Dunlap > <george.dun...@citrix.com>; Ian Jackson <ian.jack...@citrix.com>; > jbeul...@suse.com; konrad.w...@oracle.com; Paul Durrant > <paul.durr...@citrix.com>; sstabell...@kernel.org; Tim (Xen.org) > <t...@xen.org>; Wei Liu <wei.l...@citrix.com> > Subject: [RFC 0/6] Rangeset generalisation > > From: Andrii Anisov <andrii_ani...@epam.com> > > Rangesets in XEN seems to be a pretty generic thing slightly poisoned with. > domain specific funtionality in initialization and deinitialization code. > > So make the rangeset code generic with moving domain specific code to > common/domain.c
Any particular reason this series is RFC? The cleanup seems a good thing to do to me. Paul > > Andrii Anisov (6): > rangeset_new() refactoring > rangeset_destroy() refactoring > Drop rangeset_domain_initialise() > rangeset_domain_destroy() refactoring > rangeset_domain_printk() refactoring > Drop domain remains from rangeset > > xen/arch/x86/domain.c | 2 +- > xen/arch/x86/hvm/ioreq.c | 6 ++--- > xen/arch/x86/mm/p2m.c | 6 ++--- > xen/arch/x86/setup.c | 4 +-- > xen/common/domain.c | 48 +++++++++++++++++++++++++++++++---- > xen/common/keyhandler.c | 2 +- > xen/common/rangeset.c | 63 +++++++++++++++----------------------------- > -- > xen/include/xen/domain.h | 9 +++++++ > xen/include/xen/rangeset.h | 42 +++++++++++++++---------------- > 9 files changed, 102 insertions(+), 80 deletions(-) > > -- > 2.7.4 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel
