xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Olaf Hering <olaf@aepfle.de>
To: xen-devel@lists.xensource.com
Subject: [PATCH 0 of 2] remove type from mem_event
Date: Mon, 20 Feb 2012 22:18:00 +0100	[thread overview]
Message-ID: <patchbomb.1329772680@probook.site> (raw)


The intention of the first patch was to shrink mem_event_st to make room
for more events in the ring buffer. But since type is just u16 and the
struct would need much more shrinking to get more events per ring this
goal was not reached.

Now both patches just serve as cleanup.


Changes:
mem_event: remove type member
mem_event: use C99 initializers for mem_event_request_t users

 xen/arch/x86/hvm/hvm.c         |    6 +-----
 xen/arch/x86/mm/mem_sharing.c  |    3 +--
 xen/arch/x86/mm/p2m.c          |   12 ++----------
 xen/include/public/mem_event.h |    8 +-------
 4 files changed, 5 insertions(+), 24 deletions(-)

             reply	other threads:[~2012-02-20 21:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-20 21:18 Olaf Hering [this message]
2012-02-20 21:18 ` [PATCH 1 of 2] mem_event: remove type member Olaf Hering
2012-02-20 21:18 ` [PATCH 2 of 2] mem_event: use C99 initializers for mem_event_request_t users Olaf Hering
2012-02-23 15:56 ` [PATCH 0 of 2] remove type from mem_event Tim Deegan

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=patchbomb.1329772680@probook.site \
    --to=olaf@aepfle.de \
    --cc=xen-devel@lists.xensource.com \
    /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).