All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: kvm-ppc@vger.kernel.org
Subject: Re: [PATCH] target-ppc: Update slb array with correct index values.
Date: Mon, 19 Aug 2013 07:37:06 +0000	[thread overview]
Message-ID: <874nam5ei5.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <1376245011-20008-1-git-send-email-aneesh.kumar@linux.vnet.ibm.com>

Alexander Graf <agraf@suse.de> writes:

> On 11.08.2013, at 20:16, Aneesh Kumar K.V wrote:
>
>> From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
>> 
>> Without this, a value of rb=0 and rs=0, result in us replacing the 0th index
>> 
>> Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
>
> Wrong mailing list again ;).

Will post the series again with updated commit message to the qemu list.

>
>> ---
>> 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;
>> +            /*
>> +             * KVM_GET_SREGS doesn't retun slb entry with slot information
>> +             * same as index. So don't depend on the slot information in
>> +             * the returned value.
>
> This is the generating code in book3s_pr.c:
>
>         if (vcpu->arch.hflags & BOOK3S_HFLAG_SLB) {
>                 for (i = 0; i < 64; i++) {
>                         sregs->u.s.ppc64.slb[i].slbe = vcpu->arch.slb[i].orige | i;
>                         sregs->u.s.ppc64.slb[i].slbv = vcpu->arch.slb[i].origv;
>                 }
>
> Where exactly did you see broken slbe entries?
>

I noticed this when adding support for guest memory dumping via qemu gdb
server. Now the array we get would look like below

slbe0 slbv0
slbe1 slbv1
0000  00000
0000  00000

Once we get an array like that when we hit the third value we will
replace the 0th entry, that is [slbe0 slbv0]. That resulted in failed
translation of the address by qemu gdb server. 


-aneesh


  reply	other threads:[~2013-08-19  7:37 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-11 18:28 [PATCH] target-ppc: Update slb array with correct index values Aneesh Kumar K.V
2013-08-19  7:37 ` Aneesh Kumar K.V [this message]
2013-08-19  8:21   ` Alexander Graf
2013-08-19  8:21     ` Alexander Graf
2013-08-20 13:57     ` Aneesh Kumar K.V
2013-08-20 13:57       ` Aneesh Kumar K.V
2013-08-21  7:02       ` Alexander Graf
2013-08-21  7:02         ` Alexander Graf
2013-08-21  9:07         ` Aneesh Kumar K.V
2013-08-21  9:19           ` Aneesh Kumar K.V
2013-08-21  5:11     ` Paul Mackerras
2013-08-21  5:11       ` Paul Mackerras
2013-08-21  7:37       ` Alexander Graf
2013-08-21  7:37         ` Alexander Graf
2013-08-21  7:42         ` Alexander Graf
2013-08-21  7:42           ` Alexander Graf
2013-08-21  9:25         ` Paul Mackerras
2013-08-21  9:25           ` Paul Mackerras
2013-08-21 10:03           ` Alexander Graf
2013-08-21 10:03             ` Alexander Graf
2013-08-21 15:59             ` Aneesh Kumar K.V
2013-08-21 15:59               ` Aneesh Kumar K.V
2013-08-21 23:32               ` Alexander Graf
2013-08-21 23:32                 ` Alexander Graf
2013-08-22 13:20                 ` Aneesh Kumar K.V
2013-08-22 13:32                   ` Aneesh Kumar K.V
2013-08-22 16:36                   ` Alexander Graf
2013-08-22 16:36                     ` 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=874nam5ei5.fsf@linux.vnet.ibm.com \
    --to=aneesh.kumar@linux.vnet.ibm.com \
    --cc=kvm-ppc@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.