linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 1/2] powerpc/book3e-64: hv exceptions aren't MASKABLE
Date: Fri, 20 May 2011 14:39:47 -0500	[thread overview]
Message-ID: <20110520143947.763ff4ad@schlenkerla.am.freescale.net> (raw)
In-Reply-To: <029E9D3E-D310-4DB6-9D0C-5E59705B2676@kernel.crashing.org>

On Fri, 20 May 2011 14:36:09 -0500
Kumar Gala <galak@kernel.crashing.org> wrote:

> 
> On May 20, 2011, at 2:00 PM, Scott Wood wrote:
> 
> > In general we will not have EE soft-disabled or be napping when
> > these exceptions happen, but still it is not correct.
> > 
> > The guest doorbell exceptions can only be triggered with MSR[GS]=1,
> > and thus for host kernel nesting purposes are base-level exceptions.
> > 
> > Note that ehpriv and hypercall are triggerable from normal userspace.
> > I tested that the process gets properly signalled in this case.
> > 
> > Signed-off-by: Scott Wood <scottwood@freescale.com>
> > ---
> > arch/powerpc/include/asm/reg_booke.h |    2 +
> > arch/powerpc/kernel/exceptions-64e.S |   67 ++++++++++++++++++++++++++--------
> > 2 files changed, 53 insertions(+), 16 deletions(-)
> 
> Can you look at a similar patch for 32-bit fsl-booke so we handle HV exceptions if they happen to get generated, maybe something already exists for KVM.

Yes.

-Scott

  reply	other threads:[~2011-05-20 19:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-20 19:00 [PATCH 1/2] powerpc/book3e-64: hv exceptions aren't MASKABLE Scott Wood
2011-05-20 19:36 ` Kumar Gala
2011-05-20 19:39   ` Scott Wood [this message]
2011-05-20 22:30 ` 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=20110520143947.763ff4ad@schlenkerla.am.freescale.net \
    --to=scottwood@freescale.com \
    --cc=galak@kernel.crashing.org \
    --cc=linuxppc-dev@lists.ozlabs.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).