qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Blue Swirl" <blauwirbel@gmail.com>
To: "J. Mayer" <l_indien@magic.fr>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Updated >2G memory patch
Date: Sun, 30 Sep 2007 10:15:02 +0300	[thread overview]
Message-ID: <f43fc5580709300015j4f427efs34bfd0b728120ecc@mail.gmail.com> (raw)
In-Reply-To: <1191107818.29900.53.camel@rapid>

On 9/30/07, J. Mayer <l_indien@magic.fr> wrote:
> On Sat, 2007-09-29 at 23:43 +0100, Paul Brook wrote:
> > > > Also note that changing variables from int to long have strictly no
> > > > impact on 32 bits host machines, then won't help emulating more than 2
> > > > GB of RAM. Another variable type (target_phys_addr_t ?) should be used
> > > > instead.
> > >
> > > This patch should be restricted to 64-bit hosts. I don't think it's
> > > useful to emulate a 64-bit target with huge amounts of virtual and
> > > physical address space on a 32-bit host.
>
> My feeling is that if it's restricted to 64 bits host, then it's a patch
> for geeks only, that brings no useful feature to the main end-users. In
> the real world, most people are still running in 32 bits mode.

I think Qemu is a geek application. The majority of people with their
i386 Windows PCs don't know or care about, for example Sparc32
targets, or even about Qemu. The people who know about Qemu are
probably geeks, they already have some kind of need to emulate
hardware. I'd think majority of them still want to emulate an i386
target on their i386/x86_64 host. Other targets and hosts are a
minority, making the people interested in those even geekier.

But whether this patch or something else is a geek feature or not is
irrelevant. What matters is whether it breaks something or not, or if
some part of the design is objectionable. I fully agree with you that
some parts could be designed differently.

  parent reply	other threads:[~2007-09-30  7:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-29 13:04 [Qemu-devel] Updated >2G memory patch Blue Swirl
2007-09-29 13:33 ` [Qemu-devel] " Izik Eidus
2007-09-29 13:40   ` Izik Eidus
2007-09-29 13:34 ` [Qemu-devel] " J. Mayer
2007-09-29 15:54   ` Blue Swirl
2007-09-29 22:43     ` Paul Brook
2007-09-29 23:16       ` J. Mayer
2007-09-30  0:02         ` Paul Brook
2007-09-30  0:34           ` J. Mayer
2007-09-30 15:43             ` Paul Brook
2007-09-30  7:15         ` Blue Swirl [this message]
2007-09-30 12:31           ` J. Mayer
2007-09-30 14:37             ` Avi Kivity
2007-09-30 15:30             ` Blue Swirl

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=f43fc5580709300015j4f427efs34bfd0b728120ecc@mail.gmail.com \
    --to=blauwirbel@gmail.com \
    --cc=l_indien@magic.fr \
    --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).