From: "Daniel P. Berrange" <berrange@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
qemu-devel@nongnu.org, Luiz Capitulino <lcapitulino@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] qapi: add 'query-target' command to return target arch/bit size
Date: Tue, 21 Aug 2012 11:24:51 +0100 [thread overview]
Message-ID: <20120821102451.GH7982@redhat.com> (raw)
In-Reply-To: <CAFEAcA9TKXnwBTX_mKcMOXTuH8jucQSmTuNyrk6cy6iTndxZDA@mail.gmail.com>
On Tue, Aug 21, 2012 at 11:17:40AM +0100, Peter Maydell wrote:
> On 21 August 2012 11:05, Daniel P. Berrange <berrange@redhat.com> wrote:
> > On Mon, Aug 20, 2012 at 04:48:24PM -0500, Anthony Liguori wrote:
> >> "bits" is really ambiguous. What it means in QEMU (specifically the
> >> value you are returning) is probably not what you expect it to mean.
> >
> > My intent was to indicate the pointer word size for the architecture.
> > eg 64 for x86_64, ppc64, etc, and 32 and i686, ppc, etc. Probably
> > should have called it 'wordsize' or something like that
>
> This is not the same as the physical address size...
>
> > Hmm, when I looked at the header in my checkout it already
> > *is* 64 or 32 as I'd expect for the architecture in question.
> >
> > $ grep PHYS_ADDR_BITS */config-target.mak
> > alpha-softmmu/config-target.mak:TARGET_PHYS_ADDR_BITS=64
> > arm-softmmu/config-target.mak:TARGET_PHYS_ADDR_BITS=64
>
> ...eg for ARM we have a 32 bit pointer size but 40 bit physical
> addresses (on some cores) and we set TARGET_PHYS_ADDR_BITS
> to 64 in all cases.
>
> > i386-softmmu/config-target.mak:TARGET_PHYS_ADDR_BITS=64
>
> i386 is the other obvious "pointers are 32 bit but we
> set TARGET_PHYS_ADDR_BITS wider", for about the same reasons.
Ok, so I'll just respin this patch & remove the 'bits' field entirely
so we avoid the confusion.
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
next prev parent reply other threads:[~2012-08-21 10:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-20 14:31 [Qemu-devel] [PATCH] qapi: add 'query-target' command to return target arch/bit size Daniel P. Berrange
2012-08-20 15:47 ` [Qemu-devel] For 1.2: " Eric Blake
2012-08-20 19:02 ` [Qemu-devel] " Luiz Capitulino
2012-08-21 10:07 ` Daniel P. Berrange
2012-08-21 12:53 ` Luiz Capitulino
2012-08-21 13:07 ` Daniel P. Berrange
2012-08-22 13:20 ` Anthony Liguori
2012-08-20 21:48 ` Anthony Liguori
2012-08-21 10:05 ` Daniel P. Berrange
2012-08-21 10:17 ` Peter Maydell
2012-08-21 10:24 ` Daniel P. Berrange [this message]
2012-08-21 13:21 ` Anthony Liguori
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=20120821102451.GH7982@redhat.com \
--to=berrange@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=lcapitulino@redhat.com \
--cc=peter.maydell@linaro.org \
--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).