xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Patrick Colp <pjcolp@cs.ubc.ca>
To: Tim Deegan <Tim.Deegan@citrix.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH] Use fixed-width types in the memory event interface
Date: Tue, 29 Jun 2010 07:28:24 -0700	[thread overview]
Message-ID: <AANLkTimTNhdoVWa7APPGvr2uSY0ikRtmelB2GuhhIiWQ@mail.gmail.com> (raw)
In-Reply-To: <20100629134707.GF31695@whitby.uk.xensource.com>

On 29 June 2010 06:47, Tim Deegan <Tim.Deegan@citrix.com> wrote:
> Set the types in the public memory_event header file to use fixed-sized
> and self-aligned fields rather than "unsigned long".  AIUI this feature
> only works with 64-bit hypervisors but I think this change will be
> necessary to use 32-on-64 dom0 tools.
>
> This breaks compatibility with older builds of the tools, but I can't
> see any way to avoid it short of __attribute__((__packed__)).
>
> I'd like an ack/nack from Patrick on this, please.
>
> Signed-off-by: Tim Deegan <Tim.Deegan@citrix.com>

Acked-by: Patrick Colp <pjcolp@cs.ubc.ca>



> diff -r 7b00193bd033 xen/include/public/mem_event.h
> --- a/xen/include/public/mem_event.h    Mon Jun 28 17:40:16 2010 +0100
> +++ b/xen/include/public/mem_event.h    Tue Jun 29 14:38:06 2010 +0100
> @@ -40,14 +40,14 @@
>
>
>  typedef struct mem_event_shared_page {
> -    int port;
> +    uint32_t port;
>  } mem_event_shared_page_t;
>
>  typedef struct mem_event_st {
> -    unsigned long gfn;
> -    unsigned long offset;
> -    unsigned long p2mt;
> -    int vcpu_id;
> +    uint64_t gfn;
> +    uint64_t offset;
> +    uint32_t p2mt;
> +    int32_t vcpu_id;
>     uint64_t flags;
>  } mem_event_request_t, mem_event_response_t;
>
>
>

  reply	other threads:[~2010-06-29 14:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-29 13:47 [PATCH] Use fixed-width types in the memory event interface Tim Deegan
2010-06-29 14:28 ` Patrick Colp [this message]
2010-06-29 14:37   ` Patrick Colp
2010-06-29 14:52     ` Keir Fraser

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=AANLkTimTNhdoVWa7APPGvr2uSY0ikRtmelB2GuhhIiWQ@mail.gmail.com \
    --to=pjcolp@cs.ubc.ca \
    --cc=Tim.Deegan@citrix.com \
    --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).