From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Alexander Graf <agraf@suse.de>, Paul Mackerras <paulus@samba.org>
Cc: "kvm-ppc\@vger.kernel.org" <kvm-ppc@vger.kernel.org>,
"kvm\@vger.kernel.org list" <kvm@vger.kernel.org>
Subject: Re: [PATCH] target-ppc: Update slb array with correct index values.
Date: Wed, 21 Aug 2013 21:29:31 +0530 [thread overview]
Message-ID: <87vc2zkpb0.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <3D410934-51C0-43D3-BC5B-BC3B40D2C8B8@suse.de>
Alexander Graf <agraf@suse.de> writes:
....
>>
>> On HV KVM yes, that would be the end of the list, but PR KVM could
>> give you entry 0 containing esid==0 and vsid==0 followed by valid
>> entries. Perhaps the best approach is to ignore any entries with
>> SLB_ESID_V clear.
>
> That means we don't clear entries we don't receive from the kernel because they're V=0 but which were V=1 before. Which with the current code is probably already broken.
>
> So yes, clear all cached entries first (to make sure we have no stale
> ones), then loop through all and only add entries with V=1 should fix
> everything for PR as well as HV.
This is more or less what the patch is doing. The kernel already
does memset of all the slb entries. The only difference is we don't
depend on the slb index in the return value. Instead we just use the
array index as the slb index. Do we really need to make sure the slb
index remain same ?
-aneesh
next prev parent reply other threads:[~2013-08-21 15:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1376245011-20008-1-git-send-email-aneesh.kumar@linux.vnet.ibm.com>
[not found] ` <8810AF54-BB64-4313-AD32-C42608527B38@suse.de>
[not found] ` <874nam5ei5.fsf@linux.vnet.ibm.com>
2013-08-19 8:21 ` [PATCH] target-ppc: Update slb array with correct index values Alexander Graf
2013-08-20 13:57 ` Aneesh Kumar K.V
2013-08-21 7:02 ` Alexander Graf
2013-08-21 9:07 ` Aneesh Kumar K.V
2013-08-21 5:11 ` Paul Mackerras
2013-08-21 7:37 ` Alexander Graf
2013-08-21 7:42 ` Alexander Graf
2013-08-21 9:25 ` Paul Mackerras
2013-08-21 10:03 ` Alexander Graf
2013-08-21 15:59 ` Aneesh Kumar K.V [this message]
2013-08-21 23:32 ` Alexander Graf
2013-08-22 13:20 ` Aneesh Kumar K.V
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=87vc2zkpb0.fsf@linux.vnet.ibm.com \
--to=aneesh.kumar@linux.vnet.ibm.com \
--cc=agraf@suse.de \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=paulus@samba.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