All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: xen-devel@lists.xen.org
Cc: keir@xen.org, tim@xen.org, ian.jackson@eu.citrix.com,
	jbeulich@suse.com, "Wei Liu" <wei.liu2@citrix.com>,
	"Roger Pau Monné" <roger.pau@citrix.com>
Subject: Re: [PATCH DOCDAY] netif.h: describe request/response structures in terms of binary layout
Date: Wed, 25 Feb 2015 12:34:45 +0000	[thread overview]
Message-ID: <1424867685.20243.87.camel@citrix.com> (raw)
In-Reply-To: <1424866610-27163-1-git-send-email-ian.campbell@citrix.com>

On Wed, 2015-02-25 at 12:16 +0000, Ian Campbell wrote:
> In RFC style, rather than relying on the implicit assumptions of a
> particular C ABI.
> 
> I have also confirmed, using the Python gdb extension technique in
> [0], that the struct offsets (in a Linux binary at least) are the same
> as described here.
[...]
> [] http://stackoverflow.com/questions/9788679/how-to-get-the-relative-adress-of-a-field-in-a-structure-dump-c,

I had intended after the cut to include for reference:

struct xen_netif_tx_request {
    gref => 0
    offset => 4
    flags => 6
    id => 8
    size => 10
}
struct xen_netif_extra_info {
    type => 0
    flags => 1
    u => 2
}
struct xen_netif_tx_response {
    id => 0
    status => 2
}
struct xen_netif_rx_request {
    id => 0
    gref => 4
}
struct xen_netif_rx_response {
    id => 0
    offset => 2
    flags => 4
    status => 6
}

(same for all arches, of course)

Ian.

  parent reply	other threads:[~2015-02-25 12:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-25 12:16 [PATCH DOCDAY] netif.h: describe request/response structures in terms of binary layout Ian Campbell
2015-02-25 12:23 ` Andrew Cooper
2015-02-25 12:37   ` Ian Campbell
2015-02-25 12:34 ` Ian Campbell [this message]
2015-02-25 12:48 ` Jürgen Groß
2015-02-25 12:56   ` Ian Campbell
2015-02-25 12:59 ` Andrew Cooper
2015-02-25 13:19   ` Ian Campbell
2015-02-25 13:17 ` Wei Liu

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=1424867685.20243.87.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=jbeulich@suse.com \
    --cc=keir@xen.org \
    --cc=roger.pau@citrix.com \
    --cc=tim@xen.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.