All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Graf <agraf@suse.de>
To: kvm-ppc@vger.kernel.org
Subject: Re: [PATCH] KVM: PPC: Not optimizing MSR_CE and MSR_DE with paravirt.
Date: Wed, 16 May 2012 09:11:44 +0000	[thread overview]
Message-ID: <4FB36F50.3070801@suse.de> (raw)
In-Reply-To: <1337067442-26625-1-git-send-email-bharat.bhushan@freescale.com>

On 05/16/2012 10:42 AM, Bhushan Bharat-R65777 wrote:
>
>> -----Original Message-----
>> From: kvm-ppc-owner@vger.kernel.org [mailto:kvm-ppc-owner@vger.kernel.org] On
>> Behalf Of Alexander Graf
>> Sent: Tuesday, May 15, 2012 8:01 PM
>> To: Bhushan Bharat-R65777
>> Cc: kvm-ppc@vger.kernel.org; Bhushan Bharat-R65777
>> Subject: Re: [PATCH] KVM: PPC: Not optimizing MSR_CE and MSR_DE with paravirt.
>>
>> On 05/15/2012 09:37 AM, Bharat Bhushan wrote:
>>> From: Bhushan Bharat-R65777<R65777@freescale.com>
>>>
>>> If there is pending critical or machine check interrupt then guest
>>> would like to capture it when guest enable MSR.CE and MSR_ME respectively.
>>> Also as mostly MSR_CE and MSR_ME are updated with rfi/rfci/rfmii which
>>> anyway traps so removing the the paravirt optimization for MSR.CE and
>>> MSR.ME.
>> It's only not safe for e500mc and above, right?
> For e500mc and above the paravirt emulation code will not come into picture, And critical and machine check interrupt will happen only if MSR have corresponding bits set. So they are already safe. Is not it?

Yup, though it might be worth documenting the fact with a few #ifdef's, 
in case anyone wants to run PR KVM on e500mc ever.

>
>> E500v2 and book3s should be
>> fine.
> And with this patch e500v2 will be fine? Not sure of book3s :).

Well, e500v2 has edge triggered MCs, no? MSR.CE is unsafe however, as 
criticals are basically the same as externals.


Alex


  parent reply	other threads:[~2012-05-16  9:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-15  7:49 [PATCH] KVM: PPC: Not optimizing MSR_CE and MSR_DE with paravirt Bharat Bhushan
2012-05-15 14:31 ` Alexander Graf
2012-05-16  8:42 ` Bhushan Bharat-R65777
2012-05-16  9:11 ` Alexander Graf [this message]
2012-05-16 12:27 ` Sethi Varun-B16395
2012-05-16 12:47 ` Alexander Graf
2012-05-16 15:13 ` Sethi Varun-B16395
2012-05-16 22:07 ` Scott Wood
2012-05-17 11:03 ` Sethi Varun-B16395

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=4FB36F50.3070801@suse.de \
    --to=agraf@suse.de \
    --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.