qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Nathan Whitehorn <nwhitehorn@freebsd.org>
To: Alexander Graf <agraf@suse.de>
Cc: qemu-ppc@nongnu.org, QEMU Developers <qemu-devel@nongnu.org>,
	David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [Qemu-devel] [PATCH] PPC: Fix large page support in TCG
Date: Fri, 09 Mar 2012 08:30:41 -0600	[thread overview]
Message-ID: <4F5A1411.2040300@freebsd.org> (raw)
In-Reply-To: <E298DFF4-9E4C-4F24-89EA-DE35D3B50EC8@suse.de>

[-- Attachment #1: Type: text/plain, Size: 1997 bytes --]

On 03/09/12 07:13, Alexander Graf wrote:
> On 09.03.2012, at 04:42, David Gibson wrote:
>
>> On Thu, Mar 08, 2012 at 09:24:53AM -0600, Nathan Whitehorn wrote:
>>> On Mar 7, 2012, at 7:25 PM, David Gibson wrote:
>>>
>>>> On Sat, Mar 03, 2012 at 10:39:34AM -0600, Nathan Whitehorn wrote:
>>>>> Fix large page support in TCG. The old code would overwrite the
>>>>> large page table entry with the fake 4 KB
>>>>> one generated here whenever the ref/change bits were updated,
>>>>> causing it to point to the wrong area of memory. Instead of creating
>>>>> a fake PTE, just update the real address at the end.
>>>>>
>>>>> Signed-off-by: Nathan Whitehorn<nwhitehorn@freebsd.org>
>>>> Hrm.  This looks like a cleaner way of handling things, but I don't
>>>> really follow what exactly was going wrong in the old way.  Can you
>>>> spell out in more detail where the modified pte1 value caused
>>>> problems?
>>> The problem was that pte1 would get extra bits added into it in
>>> _find_pte() to produce a new, fake 4KB page table entry. When the
>>> ref/change bits were updated, pte1 would be written back to the page
>>> table -- *including* the bits added to make a fake 4K page. At the
>>> next access, since this function does not clear the low bits of
>>> large pages (which is probably itself a bug) when it interprets
>>> them, the generated address would be the large page base, ored with
>>> the large page remainder for this access, ored with the large page
>>> remainder from the *previous* access, etc. and you would get a
>>> progressively more bogus address in the end.
>> Ah, yes, I see it now.  Good catch.
>>
>> Acked-by: David Gibson<david@gibson.drobpear.id.au>
> Hrm - the patch doesn't apply for me. Could you please resend as something that's applyable? :)
> Also, please make sure to always CC qemu-ppc on ppc patches, otherwise there's a good chance they slip off my radar.
>
>
> Alex
>
Weird. I've provided it as an attachment, which should hopefully work 
this time.
-Nathan


[-- Attachment #2: 0005-Fix-large-page-support-in-TCG.-The-old-code-would-ov.patch --]
[-- Type: text/plain, Size: 1567 bytes --]

Fix large page support in TCG. The old code would overwrite the large page
table entry with the fake 4 KB one generated here whenever the ref/change bits
were updated, causing it to point to the wrong area of memory.

Signed-off-by: Nathan Whitehorn <nwhitehorn@freebsd.org>
---
 target-ppc/helper.c |   11 +++++------
 1 files changed, 5 insertions(+), 6 deletions(-)

diff --git a/target-ppc/helper.c b/target-ppc/helper.c
index 928fbcf..0f5ad2e 100644
--- a/target-ppc/helper.c
+++ b/target-ppc/helper.c
@@ -597,12 +597,6 @@ static inline int _find_pte(CPUState *env, mmu_ctx_t *ctx, int is_64b, int h,
                 pte1 = ldq_phys(env->htab_base + pteg_off + (i * 16) + 8);
             }
 
-            /* We have a TLB that saves 4K pages, so let's
-             * split a huge page to 4k chunks */
-            if (target_page_bits != TARGET_PAGE_BITS)
-                pte1 |= (ctx->eaddr & (( 1 << target_page_bits ) - 1))
-                        & TARGET_PAGE_MASK;
-
             r = pte64_check(ctx, pte0, pte1, h, rw, type);
             LOG_MMU("Load pte from " TARGET_FMT_lx " => " TARGET_FMT_lx " "
                     TARGET_FMT_lx " %d %d %d " TARGET_FMT_lx "\n",
@@ -678,6 +672,11 @@ static inline int _find_pte(CPUState *env, mmu_ctx_t *ctx, int is_64b, int h,
         }
     }
 
+    /* We have a TLB that saves 4K pages, so let's
+     * split a huge page to 4k chunks */
+    if (target_page_bits != TARGET_PAGE_BITS)
+	ctx->raddr |= (ctx->eaddr & (( 1 << target_page_bits ) - 1))
+		& TARGET_PAGE_MASK;
     return ret;
 }
 
-- 
1.7.9


  reply	other threads:[~2012-03-09 14:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-03 16:39 [Qemu-devel] [PATCH] PPC: Fix large page support in TCG Nathan Whitehorn
2012-03-03 18:07 ` Andreas Färber
2012-03-07 15:41   ` Alexander Graf
2012-03-08  1:25 ` David Gibson
2012-03-08 15:24   ` Nathan Whitehorn
2012-03-09  3:42     ` David Gibson
2012-03-09 13:13       ` Alexander Graf
2012-03-09 14:30         ` Nathan Whitehorn [this message]
2012-03-09 18:32           ` Alexander Graf

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=4F5A1411.2040300@freebsd.org \
    --to=nwhitehorn@freebsd.org \
    --cc=agraf@suse.de \
    --cc=david@gibson.dropbear.id.au \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@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).