From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoffer Dall Subject: Re: [PATCH v3] KVM: Specify byte order for KVM_EXIT_MMIO Date: Sun, 2 Feb 2014 13:02:51 -0800 Message-ID: <20140202210251.GD3570@cbox> References: <1390926522-18267-1-git-send-email-christoffer.dall@linaro.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: kvm-devel , kvm-ppc , "kvmarm@lists.cs.columbia.edu" , Patch Tracking , Marc Zyngier , Alexander Graf , Paolo Bonzini , "gleb@kernel.org" To: Peter Maydell Return-path: Content-Disposition: inline In-Reply-To: Sender: kvm-ppc-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On Sun, Feb 02, 2014 at 12:50:47PM +0000, Peter Maydell wrote: > On 28 January 2014 16:28, Christoffer Dall wrote: > > diff --git a/Documentation/virtual/kvm/api.txt b/Documentation/virtual/kvm/api.txt > > index 366bf4b..e11f09d 100644 > > --- a/Documentation/virtual/kvm/api.txt > > +++ b/Documentation/virtual/kvm/api.txt > > @@ -2565,6 +2565,10 @@ executed a memory-mapped I/O instruction which could not be satisfied > > by kvm. The 'data' member contains the written data if 'is_write' is > > true, and should be filled by application code otherwise. > > > > +The 'data' member contains, in its first 'len' bytes, the value as it would > > +appear if the VCPU performed a load or store of the appropriate width directly > > +to the byte array. > > I don't think you need my acked-by as such (though if you want it you > have it), but since I was one of the people arguing in this thread I guess > I should say specifically that I'm happy with this wording. > Paolo, Gleb, Will you apply this one directly (assuming you also agree) or do you want me to include it as part of a pull request? Thanks, -Christoffer