qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: Collin Walling <walling@linux.ibm.com>
Cc: Pierre Morel <pmorel@linux.ibm.com>,
	qemu-s390x@nongnu.org, borntraeger@de.ibm.com,
	Thomas Huth <thuth@redhat.com>,
	qemu-devel@nongnu.org, Yi Min Zhao <zyimin@linux.ibm.com>
Subject: Re: [Qemu-devel] [PATCH v2] s390x/pci: add common fmb
Date: Thu, 13 Dec 2018 15:59:37 +0100	[thread overview]
Message-ID: <20181213155937.1884ded4.cohuck@redhat.com> (raw)
In-Reply-To: <a1d0ebac-346a-18e0-b05b-42d2b051cff4@linux.ibm.com>

On Wed, 12 Dec 2018 15:25:57 -0500
Collin Walling <walling@linux.ibm.com> wrote:

> On 11/30/2018 04:27 AM, Cornelia Huck wrote:
> > On Fri, 30 Nov 2018 10:23:14 +0100
> > Pierre Morel <pmorel@linux.ibm.com> wrote:
> >   
> >> On 31/10/2018 11:49, Cornelia Huck wrote:  
> >>> On Wed, 24 Oct 2018 11:58:33 +0800
> >>> Yi Min Zhao <zyimin@linux.ibm.com> wrote:
> >>>     
> >>>> 在 2018/10/24 上午5:25, Cornelia Huck 写道:    
> >>>>> On Mon, 22 Oct 2018 13:17:34 +0100
> >>>>> Thomas Huth <thuth@redhat.com> wrote:
> >>>>>       
> >>
> >> ...snip...
> >>  
> >>>> If endianness has error, I think the values must looks wrong.
> >>>> The right thing is that values increase from 0 and intervally.
> >>>>    
> >>>
> >>> Thanks for pointing me to that file; when I run under tcg, the values
> >>> indeed look like they have an endianness issue:
> >>>
> >>> Update interval: 4000 ms
> >>> Samples: 637534208
> >>> Last update TOD: f4c01d0098000000
> >>>             Load operations:	10520408729537478656
> >>>            Store operations:	5980780305148018688
> >>>      Store block operations:	0
> >>>          Refresh operations:	0
> >>>             Allocated pages:	0
> >>>                Mapped pages:	0
> >>>              Unmapped pages:	0
> >>>
> >>> (virtio-net-pci device on a just-booted guest)
> >>>     
> >>
> >> Hy Conny,
> >>
> >> I saw we lack a response to Thomas.
> >> Otherwise have you any remark?  
> > 
> > I don't remember anything beyond the endianess issue.
> >   
> 
> This patch looks sane to me (I've lost the parent email on my
> client, else I would've replied directly to that).
> 
> I'm currently awaiting getting my system up-and-running to test
> this thoroughly. Shall we do one more round with the endianess 
> addressed in the mean time?

Sure; I'll need to rely on your testing anyway (but I'll give it a
whirl with virtio-pci).

      reply	other threads:[~2018-12-13 14:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-22  9:02 [Qemu-devel] [PATCH v2] s390x/pci: add common fmb Yi Min Zhao
2018-10-22 12:17 ` Thomas Huth
2018-10-23  7:50   ` Yi Min Zhao
2018-10-23 21:25   ` Cornelia Huck
2018-10-24  3:58     ` Yi Min Zhao
2018-10-31 10:49       ` Cornelia Huck
2018-11-30  9:23         ` Pierre Morel
2018-11-30  9:27           ` Cornelia Huck
2018-12-12 20:25             ` Collin Walling
2018-12-13 14:59               ` Cornelia Huck [this message]

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=20181213155937.1884ded4.cohuck@redhat.com \
    --to=cohuck@redhat.com \
    --cc=borntraeger@de.ibm.com \
    --cc=pmorel@linux.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-s390x@nongnu.org \
    --cc=thuth@redhat.com \
    --cc=walling@linux.ibm.com \
    --cc=zyimin@linux.ibm.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).