From: Laurent Vivier <lvivier@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>,
Kurban Mallachiev <mallachiev@ispras.ru>
Cc: qemu-devel@nongnu.org, qemu-ppc@nongnu.org,
Alexander Graf <agraf@suse.de>
Subject: Re: [Qemu-devel] [RFC PATCH 1/1] target-ppc: Don't invalidate non-supported msr bits
Date: Thu, 30 Nov 2017 08:54:06 +0100 [thread overview]
Message-ID: <34c1ac48-0fe4-dd44-7dd8-c49bb0e510a3@redhat.com> (raw)
In-Reply-To: <20171130035841.GT3023@umbus.fritz.box>
On 30/11/2017 04:58, David Gibson wrote:
> On Wed, Nov 29, 2017 at 07:22:19PM +0300, Kurban Mallachiev wrote:
>> The msr invalidation code (commits 993eb and 2360b) inverts all
>> bits except MSR_TGPR and MSR_HVB. On non PowerPC 601 processors
>> this leads to incorrect change of excp_prefix in hreg_store_msr()
>> function. The problem is that new msr value get multiplied by msr_mask
>> and inverted msr does not, thus values of MSR_EP bit in new msr value
>> and inverted msr are distinct, so that excp_prefix changes but should
>> not.
>>
>> Signed-off-by: Kurban Mallachiev <mallachiev@ispras.ru>
>
> So, the whole logic of ppc_store_msr() / hreg_store_msr() looks much
> harier than it should be to me. Nonetheless, this definitely looks
> like an improvement over the current code.
>
> Applied to ppc-for-2.11.
>
> Laurent, could this be related to the loadvm state problems you were
> seeing in several BZs?
Thank you David, I've tried and this doesn't solve my problems.
Laurent
prev parent reply other threads:[~2017-11-30 7:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-29 16:22 [Qemu-devel] [RFC PATCH 0/1] ppc: loadvm corrupts excp_prefix Kurban Mallachiev
2017-11-29 16:22 ` [Qemu-devel] [RFC PATCH 1/1] target-ppc: Don't invalidate non-supported msr bits Kurban Mallachiev
2017-11-30 3:58 ` David Gibson
2017-11-30 7:54 ` Laurent Vivier [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=34c1ac48-0fe4-dd44-7dd8-c49bb0e510a3@redhat.com \
--to=lvivier@redhat.com \
--cc=agraf@suse.de \
--cc=david@gibson.dropbear.id.au \
--cc=mallachiev@ispras.ru \
--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).