qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "J. Mayer" <l_indien@magic.fr>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] PowerPC64 and more
Date: Fri, 22 Jul 2005 13:56:52 +0200	[thread overview]
Message-ID: <1122033412.9483.133.camel@rapid> (raw)
In-Reply-To: <42E028B3.3080400@reactos.com>

On Fri, 2005-07-22 at 00:58 +0200, Filip Navara wrote:
> J. Mayer wrote:
> 
> >On Fri, 2005-07-22 at 00:10 +0200, Filip Navara wrote:
> >  
> >
> >>J. Mayer wrote:

[...]
> >>wow, you repeated my and Fabrice's mistake once more ... think about the 
> >>code below more :)
> >>note: when you'll be done thinking or run out of ideas see my x86-64 
> >>patches that i sent to ML this morning.
> >
> >Without this patch, it crashes at the first instruction trying to access
> >the BIOS.
> >And your patch does not solve the problem:
> >on a real PowerPC 64 machine, we can use the whole 64 bits virtual
> >space.
> >We agreed with Fabrice that there should be at least one more
> >indirection in page mapping, because it would cost too much memory to
> >try to map the whole needed memory space in one table, even if we can
> >"forget" some of the middle bits in most cases.
> >  
> >
> Ok, so far so good and I agree with that (I even had the third level of 
> indirection implemented)...
> 
> >Then, you're right, this patch is ugly but allows not to crash until we
> >have a correct solution with indirect tables to get a very large virtual
> >space.
> >
> >  
> >
> ... but read it once more. You're cutting up the "index", not "index >> 
> L2_BITS".

In fact, I did not want to be too invasive outside of target-ppc
subdirectory.
Then I found that Fabrice did a patch in virt_page_find_alloc for x86_64
support
(a few lines above in the same file).
I have to admit I just duplicated this hack and it solved my crashes.
As the address that generated the crash was 0xFFFFFFFFFFFFFFFC (-4), I
just admitted
that it would prevent the crash for any address...
I even did not check if the mask was the right one, in fact...

[...]

-- 
J. Mayer <l_indien@magic.fr>
Never organized

  reply	other threads:[~2005-07-22 12:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-21 11:15 [Qemu-devel] PowerPC64 and more J. Mayer
2005-07-21 22:10 ` Filip Navara
2005-07-21 22:37   ` J. Mayer
2005-07-21 22:58     ` Filip Navara
2005-07-22 11:56       ` J. Mayer [this message]
2005-07-22  1:05     ` Joe Batt

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=1122033412.9483.133.camel@rapid \
    --to=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).