qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	i.mitsyanko@samsung.com,
	KVM devel mailing list <kvm@vger.kernel.org>,
	quintela@redhat.com,
	Developers qemu-devel <qemu-devel@nongnu.org>,
	Dmitry Solodkiy <d.solodkiy@samsung.com>,
	Anthony Liguori <anthony@codemonkey.ws>
Subject: Re: [Qemu-devel] KVM call agenda for tuesday 31
Date: Mon, 05 Mar 2012 17:47:16 +0200	[thread overview]
Message-ID: <4F54E004.5040104@redhat.com> (raw)
In-Reply-To: <4F54DF1C.605@suse.de>

On 03/05/2012 05:43 PM, Andreas Färber wrote:
> Am 05.03.2012 16:10, schrieb Avi Kivity:
> > On 03/05/2012 04:37 PM, Igor Mitsyanko wrote:
> >>> Well, can't you make sd.c target dependent?  It's not so nice, but it
> >>> does solve the problem.
> >>>
> >>
> >> OK, but it will turn qemu from it's "long term path to suppress *all*
> >> target specific code" :)
> >>
> > 
> > The other alternative is to s/target_phys_addr_t/uint64_t/ in the memory
> > API.  I think 32-on-32 is quite rare these days, so it wouldn't be much
> > of a performance issue.
>
> Maybe rare, but 32-bit ARM netbooks and tablets are gaining marketshare.
>
> Mid-term also depends on how me want to proceed with LPAE softmmu-wise
> (bump "arm" to 64-bit target_phys_addr_t, or do LPAE and AArch64 in a
> new "arm64").

I was counting on LPAE to make 32-on-32 rare.

> i386 is 64-on-32 these days already; most of the embedded targets are
> still at most 32-bit though (xtensa, mblaze, ...).

These would be 32-on-64, since the host would usually be x86.  I guess
it would be even more true when the w64 port is complete.

-- 
error compiling committee.c: too many arguments to function

  reply	other threads:[~2012-03-05 15:47 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-30 18:55 [Qemu-devel] KVM call agenda for tuesday 31 Juan Quintela
2012-01-30 23:41 ` Andreas Färber
2012-01-30 23:53   ` Anthony Liguori
2012-01-31  0:37     ` Alexander Graf
2012-01-31 10:49     ` Lluís Vilanova
2012-01-31 13:15     ` Andreas Färber
2012-01-31 14:01       ` Mitsyanko Igor
2012-08-08 16:25         ` Andreas Färber
2012-08-09  7:53           ` Igor Mitsyanko
2012-01-31 14:12       ` Anthony Liguori
2012-01-31 15:04         ` Michael S. Tsirkin
2012-01-31 15:10           ` Michael S. Tsirkin
2012-01-31 15:12         ` Paolo Bonzini
2012-02-09 22:23       ` Peter Maydell
2012-02-09 22:37         ` Anthony Liguori
2012-02-09 22:42           ` Peter Maydell
2012-02-09 23:17           ` Andreas Färber
2012-02-09 23:21             ` Alexander Graf
2012-02-21 15:33         ` Peter Maydell
2012-02-22  8:06           ` Mitsyanko Igor
2012-03-05 13:38           ` Igor Mitsyanko
2012-03-05 14:13             ` Avi Kivity
2012-03-05 14:37               ` Igor Mitsyanko
2012-03-05 15:10                 ` Avi Kivity
2012-03-05 15:15                   ` Anthony Liguori
2012-03-05 15:17                     ` Avi Kivity
2012-03-05 18:53                       ` Blue Swirl
2012-03-05 20:58                         ` malc
2012-03-05 15:20                   ` Peter Maydell
2012-03-05 15:21                     ` Avi Kivity
2012-03-05 15:27                       ` Peter Maydell
2012-03-05 15:43                   ` Andreas Färber
2012-03-05 15:47                     ` Avi Kivity [this message]
2012-03-05 15:50                     ` Peter Maydell
2012-03-05 17:27                       ` Avi Kivity
2012-03-12  9:43           ` Igor Mitsyanko
2012-03-14  9:30             ` Igor Mitsyanko
2012-03-14 10:16             ` Avi Kivity
2012-01-31 13:59   ` Anthony Liguori
2012-01-31 14:09     ` Avi Kivity
2012-01-31 14:17       ` Anthony Liguori
2012-01-31 14:44         ` Avi Kivity
2012-01-31 16:23     ` Andreas Färber

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=4F54E004.5040104@redhat.com \
    --to=avi@redhat.com \
    --cc=afaerber@suse.de \
    --cc=anthony@codemonkey.ws \
    --cc=d.solodkiy@samsung.com \
    --cc=i.mitsyanko@samsung.com \
    --cc=kvm@vger.kernel.org \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@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 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).