qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Luiz Capitulino <lcapitulino@redhat.com>,
	qemu-devel <qemu-devel@nongnu.org>
Cc: peter.maydell@linaro.org, afaerber@suse.de
Subject: Re: [Qemu-devel] [PATCH for-2.0?] target-i386: fix gdb debugging with large memory guests
Date: Tue, 18 Mar 2014 08:19:52 +0100	[thread overview]
Message-ID: <5327F398.7040509@siemens.com> (raw)
In-Reply-To: <20140317215455.2f14b61f@redhat.com>

On 2014-03-18 02:54, Luiz Capitulino wrote:
> If you start a Linux guest with more than 4GB of memory and try to look at a
> memory address, you will get an error from gdb:
> 
> (gdb) p node_data[0]->node_id
> Cannot access memory at address 0xffff88013fffd3a0
> (gdb)

I suppose this is x86-64, not 32-bit with PTE, right?

> 
> I debugged this down to x86_cpu_get_phys_page_debug(), it doesn't handle the
> case where the PDPTE has the PS bit set (although I didn't check where Linux
> sets that bit). This commit adds the PS bit handling, which fixes the problem
> for me.
> 
> Signed-off-by: Luiz capitulino <lcapitulino@redhat.com>
> ---
> 
> Two observations:
> 
>  1. This bug has always existed, so it's not a regression, so I'm not sure
>     it's worth it to fix for 2.0
> 
>  2. I'm not familiar with every detail of x86_cpu_get_phys_page_debug(),
>     so I'm not completely sure this is the right thing to do
> 
>  target-i386/helper.c | 8 ++++++++
>  1 file changed, 8 insertions(+)
> 
> diff --git a/target-i386/helper.c b/target-i386/helper.c
> index 4f447b8..9b7803f 100644
> --- a/target-i386/helper.c
> +++ b/target-i386/helper.c
> @@ -951,6 +951,13 @@ hwaddr x86_cpu_get_phys_page_debug(CPUState *cs, vaddr addr)
>                  return -1;
>          }
>  
> +        if (pdpe & PG_PSE_MASK) {
> +            page_size = 1024 * 1024 * 1024;
> +            pte = pdpe & ~( (page_size - 1) & ~0xfff);
> +            pte &= ~(PG_NX_MASK | PG_HI_USER_MASK);
> +            goto out;
> +        }

Does this also apply if we are not in long mode?

I'll check this more carefully later.

Jan

> +
>          pde_addr = ((pdpe & ~0xfff & ~(PG_NX_MASK | PG_HI_USER_MASK)) +
>                      (((addr >> 21) & 0x1ff) << 3)) & env->a20_mask;
>          pde = ldq_phys(cs->as, pde_addr);
> @@ -993,6 +1000,7 @@ hwaddr x86_cpu_get_phys_page_debug(CPUState *cs, vaddr addr)
>          pte = pte & env->a20_mask;
>      }
>  
> +out:
>      page_offset = (addr & TARGET_PAGE_MASK) & (page_size - 1);
>      paddr = (pte & TARGET_PAGE_MASK) + page_offset;
>      return paddr;
> 

-- 
Siemens AG, Corporate Technology, CT RTC ITP SES-DE
Corporate Competence Center Embedded Linux

  reply	other threads:[~2014-03-18  7:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-18  1:54 [Qemu-devel] [PATCH for-2.0?] target-i386: fix gdb debugging with large memory guests Luiz Capitulino
2014-03-18  7:19 ` Jan Kiszka [this message]
2014-03-18  7:36   ` Paolo Bonzini
2014-03-18 10:30     ` Jan Kiszka
2014-03-18 13:00       ` Luiz Capitulino
2014-03-18 14:36         ` Jan Kiszka
2014-03-18 16:23           ` Luiz Capitulino
2014-03-18 16:37             ` Paolo Bonzini
2014-03-18 16:45               ` Jan Kiszka
2014-03-18 12:49   ` Luiz Capitulino

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=5327F398.7040509@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=afaerber@suse.de \
    --cc=lcapitulino@redhat.com \
    --cc=peter.maydell@linaro.org \
    --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).