From: Scott Wood <scottwood@freescale.com>
To: Scott Wood <scottwood@freescale.com>
Cc: Alexander Graf <agraf@suse.de>,
kvm-ppc@vger.kernel.org, kvm@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org,
Mihai Caraman <mihai.caraman@freescale.com>
Subject: Re: [PATCH] kvm/ppc/booke64: Hard disable interrupts when entering the guest
Date: Fri, 03 May 2013 23:53:47 +0000 [thread overview]
Message-ID: <1367625227.19391.16@snotra> (raw)
In-Reply-To: <1367624723-22456-1-git-send-email-scottwood@freescale.com> (from scottwood@freescale.com on Fri May 3 18:45:23 2013)
On 05/03/2013 06:45:23 PM, Scott Wood wrote:
> While we could just set PACA_IRQ_HARD_DIS after an exit to compensate,
> instead hard-disable interrupts before entering the guest. This way,
> we won't have to worry about interactions if we take an interrupt
> during the guest entry code. While I don't see any obvious
> interactions, it could change in the future (e.g. it would be bad if
> the non-hv code were used on 64-bit or if 32-bit guest lazy interrupt
> disabling, since the non-hv code changes IVPR among other things).
s/32-bit guest lazy/32-bit gets lazy/
-Scott
WARNING: multiple messages have this Message-ID (diff)
From: Scott Wood <scottwood@freescale.com>
To: Scott Wood <scottwood@freescale.com>
Cc: Mihai Caraman <mihai.caraman@freescale.com>,
linuxppc-dev@lists.ozlabs.org, Alexander Graf <agraf@suse.de>,
kvm-ppc@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [PATCH] kvm/ppc/booke64: Hard disable interrupts when entering the guest
Date: Fri, 3 May 2013 18:53:47 -0500 [thread overview]
Message-ID: <1367625227.19391.16@snotra> (raw)
In-Reply-To: <1367624723-22456-1-git-send-email-scottwood@freescale.com> (from scottwood@freescale.com on Fri May 3 18:45:23 2013)
On 05/03/2013 06:45:23 PM, Scott Wood wrote:
> While we could just set PACA_IRQ_HARD_DIS after an exit to compensate,
> instead hard-disable interrupts before entering the guest. This way,
> we won't have to worry about interactions if we take an interrupt
> during the guest entry code. While I don't see any obvious
> interactions, it could change in the future (e.g. it would be bad if
> the non-hv code were used on 64-bit or if 32-bit guest lazy interrupt
> disabling, since the non-hv code changes IVPR among other things).
s/32-bit guest lazy/32-bit gets lazy/
-Scott=
WARNING: multiple messages have this Message-ID (diff)
From: Scott Wood <scottwood@freescale.com>
To: Scott Wood <scottwood@freescale.com>
Cc: Alexander Graf <agraf@suse.de>, <kvm-ppc@vger.kernel.org>,
<kvm@vger.kernel.org>, <linuxppc-dev@lists.ozlabs.org>,
Mihai Caraman <mihai.caraman@freescale.com>
Subject: Re: [PATCH] kvm/ppc/booke64: Hard disable interrupts when entering the guest
Date: Fri, 3 May 2013 18:53:47 -0500 [thread overview]
Message-ID: <1367625227.19391.16@snotra> (raw)
In-Reply-To: <1367624723-22456-1-git-send-email-scottwood@freescale.com> (from scottwood@freescale.com on Fri May 3 18:45:23 2013)
On 05/03/2013 06:45:23 PM, Scott Wood wrote:
> While we could just set PACA_IRQ_HARD_DIS after an exit to compensate,
> instead hard-disable interrupts before entering the guest. This way,
> we won't have to worry about interactions if we take an interrupt
> during the guest entry code. While I don't see any obvious
> interactions, it could change in the future (e.g. it would be bad if
> the non-hv code were used on 64-bit or if 32-bit guest lazy interrupt
> disabling, since the non-hv code changes IVPR among other things).
s/32-bit guest lazy/32-bit gets lazy/
-Scott
next prev parent reply other threads:[~2013-05-03 23:53 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-03 23:45 [PATCH] kvm/ppc/booke64: Hard disable interrupts when entering the guest Scott Wood
2013-05-03 23:45 ` Scott Wood
2013-05-03 23:45 ` Scott Wood
2013-05-03 23:53 ` Scott Wood [this message]
2013-05-03 23:53 ` Scott Wood
2013-05-03 23:53 ` Scott Wood
2013-05-04 7:11 ` Caraman Mihai Claudiu-B02008
2013-05-04 7:11 ` Caraman Mihai Claudiu-B02008
2013-05-04 7:11 ` Caraman Mihai Claudiu-B02008
2013-05-05 21:03 ` Benjamin Herrenschmidt
2013-05-05 21:03 ` Benjamin Herrenschmidt
2013-05-05 21:03 ` Benjamin Herrenschmidt
2013-05-06 23:53 ` Scott Wood
2013-05-06 23:53 ` Scott Wood
2013-05-06 23:53 ` Scott Wood
2013-05-07 0:03 ` Benjamin Herrenschmidt
2013-05-07 0:03 ` Benjamin Herrenschmidt
2013-05-07 0:03 ` Benjamin Herrenschmidt
2013-05-07 3:05 ` Scott Wood
2013-05-07 3:05 ` Scott Wood
2013-05-07 3:05 ` Scott Wood
2013-05-07 3:53 ` Benjamin Herrenschmidt
2013-05-07 3:53 ` Benjamin Herrenschmidt
2013-05-07 3:53 ` Benjamin Herrenschmidt
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=1367625227.19391.16@snotra \
--to=scottwood@freescale.com \
--cc=agraf@suse.de \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mihai.caraman@freescale.com \
/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.