From: Alexander Graf <agraf@suse.de>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: qemu-ppc@nongnu.org, paulus@samba.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH -V4 1/4] target-ppc: Update slb array with correct index values.
Date: Mon, 30 Sep 2013 19:40:53 +0200 [thread overview]
Message-ID: <5249B7A5.1000703@suse.de> (raw)
In-Reply-To: <87y56kdi30.fsf@linux.vnet.ibm.com>
On 09/25/2013 05:41 PM, Aneesh Kumar K.V wrote:
> Hi Alex,
>
> Any update on this ?
The patch itself never made it to the qemu-devel mailing list which I
pull things off of (through patchworks). Please resend.
Alex
>
> -aneesh
>
> "Aneesh Kumar K.V"<aneesh.kumar@linux.vnet.ibm.com> writes:
>
>> 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
>> 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 0xc000000000085330
>>
>> Signed-off-by: Aneesh Kumar K.V<aneesh.kumar@linux.vnet.ibm.com>
>> ---
>> target-ppc/kvm.c | 17 +++++++++++++++--
>> 1 file changed, 15 insertions(+), 2 deletions(-)
>>
>> diff --git a/target-ppc/kvm.c b/target-ppc/kvm.c
>> index 30a870e..1838465 100644
>> --- a/target-ppc/kvm.c
>> +++ b/target-ppc/kvm.c
>> @@ -1033,9 +1033,22 @@ int kvm_arch_get_registers(CPUState *cs)
>>
>> /* Sync SLB */
>> #ifdef TARGET_PPC64
>> + /*
>> + * The packed SLB array we get from KVM_GET_SREGS only contains
>> + * information about valid entries. So we flush our internal
>> + * copy to get rid of stale ones, then put all valid SLB entries
>> + * back in.
>> + */
>> + memset(env->slb, 0, sizeof(env->slb));
>> 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;
>> + target_ulong rs = sregs.u.s.ppc64.slb[i].slbv;
>> + /*
>> + * Only restore valid entries
>> + */
>> + if (rb& SLB_ESID_V) {
>> + ppc_store_slb(env, rb, rs);
>> + }
>> }
>> #endif
>>
>> --
>> 1.8.1.2
>
next prev parent reply other threads:[~2013-09-30 17:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1378369007-958-1-git-send-email-aneesh.kumar@linux.vnet.ibm.com>
[not found] ` <1378369007-958-2-git-send-email-aneesh.kumar@linux.vnet.ibm.com>
2013-09-25 15:41 ` [Qemu-devel] [PATCH -V4 1/4] target-ppc: Update slb array with correct index values Aneesh Kumar K.V
2013-09-30 17:40 ` Alexander Graf [this message]
2013-10-01 1:29 ` Aneesh Kumar K.V
[not found] ` <1378369007-958-3-git-send-email-aneesh.kumar@linux.vnet.ibm.com>
2013-09-30 17:48 ` [Qemu-devel] [PATCH -V4 2/4] target-ppc: Fix page table lookup with kvm enabled Alexander Graf
2013-09-30 17:50 ` Alexander Graf
2013-10-01 1:27 ` Aneesh Kumar K.V
2013-10-02 13:59 ` Alexander Graf
2013-10-07 13:58 ` Aneesh Kumar K.V
2013-10-07 14:04 ` 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=5249B7A5.1000703@suse.de \
--to=agraf@suse.de \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=paulus@samba.org \
--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).