From: "Andreas Färber" <afaerber@suse.de>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: Alexey Kardashevskiy <aik@ozlabs.ru>,
qemu-ppc@nongnu.org, Alexander Graf <agraf@suse.de>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/3] target-ppc: Update slb array with correct index values.
Date: Mon, 19 Aug 2013 14:50:30 +0200 [thread overview]
Message-ID: <52121496.50500@suse.de> (raw)
In-Reply-To: <521212C6.3070704@suse.de>
Am 19.08.2013 14:42, schrieb Andreas Färber:
> Am 19.08.2013 14:29, schrieb Aneesh Kumar K.V:
>> From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
>>
>> Without this, a value of rb=0 and rs=0, results in replacing the 0th
>
> "... rs=0 results in ..."
>
>> index. This can be observed when using gdb remote debugging support.
>>
>> (gdb) x/10i do_fork
>> 0xc000000000085330 <do_fork>: Cannot access memory at address 0xc000000000085330
>> (gdb)
>>
>> This is because when we do the slb sync via kvm_cpu_synchronize_state,
>> we overwrite the slb entry (0th entry) for 0xc00000000008533
>
> Is there a trailing 0 missing here?
>
>>
>> Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
>> ---
>> target-ppc/kvm.c | 14 ++++++++++++--
>> 1 file changed, 12 insertions(+), 2 deletions(-)
>>
>> diff --git a/target-ppc/kvm.c b/target-ppc/kvm.c
>> index 30a870e..5d4e613 100644
>> --- a/target-ppc/kvm.c
>> +++ b/target-ppc/kvm.c
>> @@ -1034,8 +1034,18 @@ int kvm_arch_get_registers(CPUState *cs)
>> /* Sync SLB */
>> #ifdef TARGET_PPC64
>> for (i = 0; i < 64; i++) {
>> - ppc_store_slb(env, sregs.u.s.ppc64.slb[i].slbe,
>> - sregs.u.s.ppc64.slb[i].slbv);
>> + target_ulong rb = sregs.u.s.ppc64.slb[i].slbe;
>
> Double space.
>
>> + /*
>> + * KVM_GET_SREGS doesn't retun slb entry with slot information
"return"
>> + * same as index. So don't depend on the slot information in
>> + * the returned value.
>> + */
>> + rb &= ~0xfff;
>> + /*
>> + * use the array index as the slot
>> + */
>> + rb |= i;
>> + ppc_store_slb(env, rb, sregs.u.s.ppc64.slb[i].slbv);
>> }
>> #endif
>>
>
> Regards,
> Andreas
>
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2013-08-19 12:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-19 12:29 [Qemu-devel] [PATCH 0/3] target-ppc: Add support for dumping guest memory using qemu gdb server Aneesh Kumar K.V
2013-08-19 12:29 ` [Qemu-devel] [PATCH 1/3] target-ppc: Update slb array with correct index values Aneesh Kumar K.V
2013-08-19 12:42 ` Andreas Färber
2013-08-19 12:50 ` Andreas Färber [this message]
2013-08-19 12:29 ` [Qemu-devel] [PATCH 2/3] target-ppc: Use #define instead of opencoding SLB valid bit Aneesh Kumar K.V
2013-08-19 12:44 ` Andreas Färber
2013-08-19 12:29 ` [Qemu-devel] [PATCH 3/3] target-ppc: Fix page table lookup with kvm enabled Aneesh Kumar K.V
2013-08-19 13:07 ` Andreas Färber
2013-08-19 13:10 ` [Qemu-devel] [PATCH 0/3] target-ppc: Add support for dumping guest memory using qemu gdb server Andreas Färber
2013-08-20 8:19 ` Aneesh Kumar K.V
2013-08-20 12:49 ` Andreas Färber
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=52121496.50500@suse.de \
--to=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=aik@ozlabs.ru \
--cc=aneesh.kumar@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).