qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Vivier <lvivier@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: Alexander Graf <agraf@suse.de>,
	qemu-ppc@nongnu.org, qemu-devel@nongnu.org,
	Andrew Jones <drjones@redhat.com>, Thomas Huth <thuth@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] ppc64: fix compressed dump with pseries kernel
Date: Thu, 4 Aug 2016 10:41:16 +0200	[thread overview]
Message-ID: <a3711400-7162-36b4-dbf6-fe1b141fb5be@redhat.com> (raw)
In-Reply-To: <20160804023800.GE9189@voom.fritz.box>



On 04/08/2016 04:38, David Gibson wrote:
> On Wed, Aug 03, 2016 at 09:55:07PM +0200, Laurent Vivier wrote:
>> If we don't provide the page size in target-ppc:cpu_get_dump_info(),
>> the default one (TARGET_PAGE_SIZE, 4KB) is used to create
>> the compressed dump. It works fine with Macintosh, but not with
>> pseries as the kernel default page size is 64KB.
>>
>> Without this patch, if we generate a compressed dump in the QEMU monitor:
>>
>>     (qemu) dump-guest-memory -z qemu.dump
>>
>> This dump cannot be read by crash:
>>
>>     # crash vmlinux qemu.dump
>>     ...
>>     WARNING: cannot translate vmemmap kernel virtual addresses:
>>              commands requiring page structure contents will fail
>>     ...
>>
>> Signed-off-by: Laurent Vivier <lvivier@redhat.com>
>> ---
>>  target-ppc/arch_dump.c | 5 +++++
>>  1 file changed, 5 insertions(+)
> 
> Urgh.. so, really the page size used by the guest kernel is a
> guest-side detail, and it's certainly possible to build a 4kiB page
> guest kernel, although 64kiB is the norm.

virtio-balloon doesn't work with 4K kernel.

> This might be the best we can do, but it'd be nice if we could probe
> or otherwise avoid relying on this assumption about the guest kernel.

I agree with you but none of the other architectures probes for the page
size.

For instance ARM: |I cc: Drew to know how he has chosen the values]

    if (arm_feature(env, ARM_FEATURE_AARCH64)) {
...
        info->page_size = (1 << 16);
...
    } else {
...
        info->page_size = (1 << 12);
...
    }

In the kernel:

arch/arm64/include/asm/page.h:

#define PAGE_SHIFT		CONFIG_ARM64_PAGE_SHIFT

arch/arm64/Kconfig:

config ARM64_PAGE_SHIFT
        int
        default 16 if ARM64_64K_PAGES
        default 14 if ARM64_16K_PAGES
        default 12

choice
        prompt "Page size"
        default ARM64_4K_PAGES
        help
          Page size (translation granule) configuration.

config ARM64_4K_PAGES
        bool "4KB"
        help
          This feature enables 4KB pages support.

config ARM64_16K_PAGES
        bool "16KB"
        help
          The system will use 16KB pages support. AArch32 emulation
          requires applications compiled with 16K (or a multiple of 16K)
          aligned segments.

config ARM64_64K_PAGES
        bool "64KB"
        help
          This feature enables 64KB pages support (4KB by default)
          allowing only two levels of page tables and faster TLB
          look-up. AArch32 emulation requires applications compiled
          with 64K aligned segments.

endchoice

I think we can't rely on the CPU state or the memory content as they can
be corrupted.

Thanks,
Laurent

  reply	other threads:[~2016-08-04  8:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-03 19:55 [Qemu-devel] [PATCH] ppc64: fix compressed dump with pseries kernel Laurent Vivier
2016-08-04  2:38 ` David Gibson
2016-08-04  8:41   ` Laurent Vivier [this message]
2016-08-05  7:49     ` David Gibson
2016-08-05  8:03       ` Laurent Vivier
2016-08-05  8:14       ` Thomas Huth
2016-08-05  9:26     ` Andrew Jones
2016-08-05  9:46       ` Laurent Vivier
2016-08-05 12:44         ` Andrew Jones
2016-08-05 10:56       ` David Gibson
2016-08-05  9:30 ` Andrew Jones

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=a3711400-7162-36b4-dbf6-fe1b141fb5be@redhat.com \
    --to=lvivier@redhat.com \
    --cc=agraf@suse.de \
    --cc=david@gibson.dropbear.id.au \
    --cc=drjones@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=thuth@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).