From: Paolo Bonzini <pbonzini@redhat.com>
To: Andrew Jones <drjones@redhat.com>, Thomas Huth <thuth@redhat.com>
Cc: kvm@vger.kernel.org, rkrcmar@redhat.com
Subject: Re: [kvm-unit-tests PATCH v2 2/4] lib/alloc: fix format warnings, add/use PRIx64
Date: Thu, 3 Mar 2016 13:36:56 +0100 [thread overview]
Message-ID: <56D82FE8.7090003@redhat.com> (raw)
In-Reply-To: <20160303122202.ki36zyfyucqxdkkp@hawk.localdomain>
On 03/03/2016 13:22, Andrew Jones wrote:
>> > So as far as I can see, the related variables (align_min et al.) are of
>> > type phys_addr_t. And phys_addr_t is defined like this:
>> >
>> > #ifdef PHYS32
>> > typedef u32 phys_addr_t;
>> > #else
>> > typedef u64 phys_addr_t;
>> > #endif
> Oh yeah... It's tempting to just blow that away
Just blow it away. Both aarch32 and x86-32 support 64-bit physical
address space through PAE and LPAE. You can do it on top of v3, but
remember to clean up the casts.
Paolo
next prev parent reply other threads:[~2016-03-03 12:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-02 18:07 [kvm-unit-tests PATCH v2 0/4] add fmt warnings to printf, and fix bad uses Andrew Jones
2016-03-02 18:07 ` [kvm-unit-tests PATCH v2 1/4] lib: *printf: warn on format/arg mismatch Andrew Jones
2016-03-02 18:07 ` [kvm-unit-tests PATCH v2 2/4] lib/alloc: fix format warnings, add/use PRIx64 Andrew Jones
2016-03-03 9:28 ` Thomas Huth
2016-03-03 12:22 ` Andrew Jones
2016-03-03 12:36 ` Paolo Bonzini [this message]
2016-03-02 18:07 ` [kvm-unit-tests PATCH v2 3/4] arm64: fix printf format warnings Andrew Jones
2016-03-03 9:41 ` Thomas Huth
2016-03-02 18:07 ` [kvm-unit-tests PATCH v2 4/4] x86: " Andrew Jones
2016-03-03 9:57 ` Thomas Huth
2016-03-03 12:26 ` Andrew Jones
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=56D82FE8.7090003@redhat.com \
--to=pbonzini@redhat.com \
--cc=drjones@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=rkrcmar@redhat.com \
--cc=thuth@redhat.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 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.