From: Andrii Anisov <andrii.anisov@gmail.com>
To: xen-devel@lists.xenproject.org
Cc: sstabellini@kernel.org, andrii_anisov@epam.com,
George.Dunlap@eu.citrix.com, andrew.cooper3@citrix.com,
ian.jackson@eu.citrix.com, tim@xen.org, paul.durrant@citrix.com,
jbeulich@suse.com, wei.liu2@citrix.com
Subject: [RFC 0/6] Rangeset generalisation
Date: Thu, 16 Feb 2017 14:03:24 +0200 [thread overview]
Message-ID: <1487246610-8298-1-git-send-email-andrii.anisov@gmail.com> (raw)
From: Andrii Anisov <andrii_anisov@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
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
next reply other threads:[~2017-02-16 12:03 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-16 12:03 Andrii Anisov [this message]
2017-02-16 12:03 ` [RFC 1/6] rangeset_new() refactoring Andrii Anisov
2017-02-16 12:14 ` Paul Durrant
2017-02-16 13:15 ` Andrii Anisov
2017-02-16 12:03 ` [RFC 2/6] rangeset_destroy() refactoring Andrii Anisov
2017-02-16 12:26 ` Paul Durrant
2017-02-16 14:26 ` Andrii Anisov
2017-02-16 14:29 ` Paul Durrant
2017-02-16 16:22 ` Andrii Anisov
2017-02-16 16:37 ` Paul Durrant
2017-02-16 12:03 ` [RFC 3/6] Drop rangeset_domain_initialise() Andrii Anisov
2017-02-16 12:03 ` [RFC 4/6] rangeset_domain_destroy() refactoring Andrii Anisov
2017-02-16 12:03 ` [RFC 5/6] rangeset_domain_printk() refactoring Andrii Anisov
2017-02-16 12:03 ` [RFC 6/6] Drop domain remains from rangeset Andrii Anisov
2017-02-16 12:29 ` [RFC 0/6] Rangeset generalisation Paul Durrant
2017-02-16 12:45 ` Andrii Anisov
2017-02-16 12:50 ` Paul Durrant
2017-02-16 13:07 ` Andrii Anisov
2017-02-16 13:24 ` Andrii Anisov
2017-02-16 14:02 ` Paul Durrant
2017-02-16 14:28 ` Andrii Anisov
2017-02-16 13:25 ` Jan Beulich
2017-02-16 13:37 ` Andrii Anisov
2017-02-16 13:42 ` Andrii Anisov
2017-02-16 14:30 ` Jan Beulich
2017-02-16 17:39 ` George Dunlap
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=1487246610-8298-1-git-send-email-andrii.anisov@gmail.com \
--to=andrii.anisov@gmail.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=andrii_anisov@epam.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=paul.durrant@citrix.com \
--cc=sstabellini@kernel.org \
--cc=tim@xen.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).