xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Xen-devel <xen-devel@lists.xen.org>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
	Wei Liu <wei.liu2@citrix.com>, Jan Beulich <JBeulich@suse.com>
Subject: [PATCH RFC for-next 0/4] Reimpliement {compat_, }create_bounce_frame() in C
Date: Mon, 8 May 2017 16:48:04 +0100	[thread overview]
Message-ID: <1494258488-30714-1-git-send-email-andrew.cooper3@citrix.com> (raw)

Bloat-o-meter reports:
  add/remove: 1/1 grow/shrink: 0/1 up/down: 1211/-2587 (-1376)
  function                                     old     new   delta
  pv_create_exception_frame                      -    1211   +1211
  asm_domain_crash_synchronous                  65       -     -65
  context_switch                              3565    1043   -2522

but as the assembly symbols aren't tagged with type/size information, it can't
spot the removal of {compat_,}create_bounce_frame() at all.

This series is based on top of the "[PATCH for-4.9 0/2] x86/pv: Misc fixes"
series, which were discovered while developing this series.

Andrew Cooper (4):
  x86/pv: Drop int80_bounce from struct pv_vcpu
  x86/pv: Introduce pv_create_exception_frame()
  x86/pv: Drop {compat_,}create_bounce_frame() and use the C version instead
  x86/pv: Implement the failsafe callback using the general path

 xen/arch/x86/domain.c              | 102 ++--------------------
 xen/arch/x86/pv/traps.c            | 152 ++++++++++++++++++++++++++++++++
 xen/arch/x86/traps.c               |  27 ------
 xen/arch/x86/x86_64/asm-offsets.c  |   1 -
 xen/arch/x86/x86_64/compat/entry.S | 116 ++-----------------------
 xen/arch/x86/x86_64/compat/traps.c |   4 -
 xen/arch/x86/x86_64/entry.S        | 173 +++++++------------------------------
 xen/arch/x86/x86_64/traps.c        |  14 ---
 xen/include/asm-x86/domain.h       |   1 -
 xen/include/asm-x86/processor.h    |   3 +-
 xen/include/xen/sched.h            |   7 --
 11 files changed, 198 insertions(+), 402 deletions(-)

-- 
2.1.4


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

             reply	other threads:[~2017-05-08 15:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-08 15:48 Andrew Cooper [this message]
2017-05-08 15:48 ` [PATCH 1/4] x86/pv: Drop int80_bounce from struct pv_vcpu Andrew Cooper
2017-05-09 14:49   ` Jan Beulich
2017-05-09 15:09     ` Andrew Cooper
2017-05-08 15:48 ` [PATCH 2/4] x86/pv: Introduce pv_create_exception_frame() Andrew Cooper
2017-05-09 15:58   ` Jan Beulich
2017-05-09 17:09     ` Andrew Cooper
2017-05-10  7:43       ` Jan Beulich
2017-05-08 15:48 ` [PATCH 3/4] x86/pv: Drop {compat_, }create_bounce_frame() and use the C version instead Andrew Cooper
2017-05-09 16:16   ` Jan Beulich
2017-05-09 17:24     ` Andrew Cooper
2017-05-10  7:50       ` Jan Beulich
2017-05-08 15:48 ` [PATCH 4/4] x86/pv: Implement the failsafe callback using the general path Andrew Cooper
2017-05-09 16:22   ` Jan Beulich

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=1494258488-30714-1-git-send-email-andrew.cooper3@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=wei.liu2@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 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).