From: Peter Xu <peterx@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
qemu-devel@nongnu.org,
Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
Subject: Re: [Qemu-devel] [PATCH] memory: use 128 bit in info mtree
Date: Tue, 14 Mar 2017 19:58:35 +0800 [thread overview]
Message-ID: <20170314115835.GD12964@pxdev.xzpeter.org> (raw)
In-Reply-To: <c8991a52-3cb5-b16a-6979-36c46d197aa8@redhat.com>
On Tue, Mar 14, 2017 at 11:26:19AM +0100, Paolo Bonzini wrote:
>
>
> On 13/03/2017 04:02, Peter Xu wrote:
> > On Sun, Mar 12, 2017 at 09:12:43PM +0200, Michael S. Tsirkin wrote:
> >> info mtree is doing 64 bit math to figure out
> >> addresses from offsets, this does not work ncorrectly
> >> incase of overflow.
> >>
> >> Overflow usually indicates a guest bug, so this is unusual
> >> but reporting correct addresses makes it easier to discover
> >> what is going on.
> >
> > A tiny issue would be that we will always dump 128 bits even if
> > nothing went wrong. IMHO That's slightly awkward. Not sure whether
> > that will confuse people since they should be thinking why we need
> > that on 64bit systems...
> >
> > Do you like below one instead? It'll keep the old interface, but just
> > warn user explicity when something wrong happens, and it's much easier
> > and obvious imho (along with a tiny cleanup):
> >
> > (the code is not tested even for compile)
>
> Looks good, can you submit it formally?
Sure! Will do.
-- peterx
next prev parent reply other threads:[~2017-03-14 11:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-12 19:12 [Qemu-devel] [PATCH] memory: use 128 bit in info mtree Michael S. Tsirkin
2017-03-12 19:16 ` no-reply
2017-03-12 19:35 ` Peter Maydell
2017-03-14 10:26 ` Paolo Bonzini
2017-03-13 3:02 ` Peter Xu
2017-03-14 10:26 ` Paolo Bonzini
2017-03-14 11:58 ` Peter Xu [this message]
2017-03-14 15:06 ` Michael S. Tsirkin
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=20170314115835.GD12964@pxdev.xzpeter.org \
--to=peterx@redhat.com \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=mst@redhat.com \
--cc=pbonzini@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 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).