qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Graf <agraf@suse.de>
To: Greg Kurz <gkurz@linux.vnet.ibm.com>
Cc: qemu-ppc@nongnu.org, aneesh.kumar@linux.vnet.ibm.com,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/4] target-ppc: htab fixes (V2)
Date: Tue, 25 Feb 2014 15:44:44 +0100	[thread overview]
Message-ID: <530CAC5C.9040005@suse.de> (raw)
In-Reply-To: <20140220175210.23576.10431.stgit@bahia.local>

Greg Kurz wrote:
> On Mon, 17 Feb 2014 14:22:14 +0100
> Greg Kurz <gkurz@linux.vnet.ibm.com> wrote:
>   
>> Hi,
>>
>> This is a new tentative for the patches 2/5 to 5/5 from the "target-ppc:
>> Add support for dumping guest memory using qemu gdb server" patchset:
>>
>> https://lists.nongnu.org/archive/html/qemu-ppc/2014-01/msg00380.html
>>
>> All patches have been rebased on the current ppc-next head (72c798d7dccc).
>>
>> To ensure proper bisectability, the following was verified for each
>> individual patch:
>> •- 32 and 64 bit build of ppc-softmmu and ppc64-softmmu (fedora 19 ppc64)
>> •- 64 bit pseries guest with KVM on a POWER7 host (fedora 19 ppc64)
>> •- 64 bit pseries guest with 64 bit TCG on a x86_64 host (fedora 19 ppc64)
>> •- 64 bit pseries guest with 32 bit TCG on a x86_64 host (fedora 19 ppc64)
>> •- 32 bit mac99 guest with 64 bit TCG on a x86_64 host (wheezy ppc)
>> •- 32 bit mac99 guest with 32 bit TCG on a x86_64 host (wheezy ppc)
>>
>> Alex,
>>
>> This should address all the requirements you expressed in your last mail.
>> Please tell me if something is missing.
>>     
>
> Alex,
>
> I have added the 32 bit build with KVM enabled to catch the remaining build
> breaks:
>
> target-ppc/kvm.c: In function 'kvmppc_hash64_read_pteg':
> target-ppc/kvm.c:1977:12: error: cast from pointer to integer of different size
>  [-Werror=pointer-to-int-cast]
> target-ppc/kvm.c: In function 'kvmppc_hash64_free_pteg':
> target-ppc/kvm.c:1990:82: error: cast to pointer from integer of different size
>  [-Werror=int-to-pointer-cast]
>
> I have folded the fix into patch 2/4.
>
> I have also fixed the SoB mess, and rebased on the current ppc-next.
>
> Hope this time, it is okay ! :)
>   

Thanks, applied to ppc-next.


Alex

      parent reply	other threads:[~2014-02-25 13:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-17 13:22 [Qemu-devel] [PATCH 0/4] target-ppc: htab fixes Greg Kurz
2014-02-17 13:22 ` [Qemu-devel] [PATCH 1/4] target-ppc: Fix htab_mask calculation Greg Kurz
2014-02-17 13:22 ` [Qemu-devel] [PATCH 2/4] target-ppc: Fix page table lookup with kvm enabled Greg Kurz
2014-02-17 13:22 ` [Qemu-devel] [PATCH 3/4] target-ppc: Change the hpte store API Greg Kurz
2014-02-17 13:22 ` [Qemu-devel] [PATCH 4/4] target-ppc: Update ppc_hash64_store_hpte to support updating in-kernel htab Greg Kurz
2014-02-20 17:52 ` [Qemu-devel] [PATCH 0/4] target-ppc: htab fixes (V2) Greg Kurz
2014-02-20 17:52   ` [Qemu-devel] [PATCH 1/4] target-ppc: Fix htab_mask calculation Greg Kurz
2014-02-20 17:52   ` [Qemu-devel] [PATCH 2/4] target-ppc: Fix page table lookup with kvm enabled Greg Kurz
2014-02-20 17:52   ` [Qemu-devel] [PATCH 3/4] target-ppc: Change the hpte store API Greg Kurz
2014-02-20 17:52   ` [Qemu-devel] [PATCH 4/4] target-ppc: Update ppc_hash64_store_hpte to support updating in-kernel htab Greg Kurz
2014-02-25 14:44   ` Alexander Graf [this message]

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=530CAC5C.9040005@suse.de \
    --to=agraf@suse.de \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=gkurz@linux.vnet.ibm.com \
    --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).