All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fam Zheng <famz@redhat.com>
To: "Bryan D. Payne" <bdpayne@acm.org>
Cc: qemu-devel@nongnu.org, lcapitulino@redhat.com
Subject: Re: [Qemu-devel] [PATCH] qmp: extend QMP to provide read/write access to physical memory
Date: Thu, 4 Dec 2014 15:38:12 +0800	[thread overview]
Message-ID: <20141204073811.GA12967@ad.nay.redhat.com> (raw)
In-Reply-To: <CAFpPvXAHNmkb15fdkfv0q-ZiQFdqw9PxPuRrgYM7GaoFkzMmMg@mail.gmail.com>

On Wed, 12/03 22:28, Bryan D. Payne wrote:
> >
> > It is critical as a transport data structure. You have to define a
> > byte-by-byte
> > layout (concerning endianness and padding) and use padding fields together
> > with
> > QEMU_PACKED, so the representation is not dependent on alignment
> 
> 
> This makes sense for network protocols.  But, in this case, the protocol is
> always taking placing over a unix socket on the localhost.  This is why I
> wasn't sure that it was necessary.
> 
> Just to be clear... the QMP connection could go over the network, but its
> only purpose is to set up the unix socket on the local machine (meaning
> that doing it over the network is kind of pointless, even if it is
> possible).  Once the unix socket is setup, the memory access protocol
> happens over that socket.

This doesn't stop the client from using a different alignment than we expect.
It's necessary to be explicit as a binary protocol.

Fam

  reply	other threads:[~2014-12-04  7:38 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-26  8:41 [Qemu-devel] [PATCH 0/1] qmp: extend QMP to provide read/write access to physical memory Bryan D. Payne
2014-11-26  8:41 ` [Qemu-devel] [PATCH 1/1] " Bryan D. Payne
2014-11-26 15:16   ` Eric Blake
2014-11-26 20:27 ` [Qemu-devel] [PATCH v2] " Bryan D. Payne
2014-11-26 20:27   ` [Qemu-devel] [PATCH] " Bryan D. Payne
2014-11-27  2:04     ` Fam Zheng
2014-12-04  3:37       ` Bryan D. Payne
2014-12-04  4:57         ` Fam Zheng
2014-12-04  6:28           ` Bryan D. Payne
2014-12-04  7:38             ` Fam Zheng [this message]
2014-12-04 16:43               ` Bryan D. Payne
2014-12-05  1:20                 ` Fam Zheng
2014-12-04  9:08         ` Markus Armbruster
2014-12-04 16:49           ` Bryan D. Payne
2014-12-05  8:44             ` Markus Armbruster
2014-12-05 21:25               ` Bryan D. Payne
2014-12-08 15:06                 ` Markus Armbruster
2014-12-09 15:12                   ` Bryan D. Payne
2014-12-11  3:33                     ` Bryan D. Payne
2014-12-11  5:45                       ` Fam Zheng
2014-12-11  6:07                         ` Bryan D. Payne
2014-12-12  2:28                         ` Bryan D. Payne
2014-12-12  3:29                           ` Fam Zheng
2014-12-01 22:10     ` Eric Blake
2014-12-03 23:07       ` Bryan D. Payne
2014-12-04 15:08         ` Eric Blake
2014-12-04 16:50           ` Bryan D. Payne
2014-12-04 18:40           ` Bryan D. Payne
2014-12-04 22:43             ` Eric Blake
2014-12-01 22:12   ` [Qemu-devel] [PATCH v2] " Eric Blake
2014-12-02  4:36     ` Bryan D. Payne
2014-12-02  5:26       ` Fam Zheng

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=20141204073811.GA12967@ad.nay.redhat.com \
    --to=famz@redhat.com \
    --cc=bdpayne@acm.org \
    --cc=lcapitulino@redhat.com \
    --cc=qemu-devel@nongnu.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.