From: Alexander Graf <agraf@suse.de>
To: Bharat Bhushan <Bharat.Bhushan@freescale.com>, kvm-ppc@vger.kernel.org
Cc: kvm@vger.kernel.org, scottwood@freescale.com, stuart.yoder@freescale.com
Subject: Re: [PATCH v2] kvm: ppc: bookehv: Save restore SPRN_SPRG9 on guest entry exit
Date: Thu, 24 Jul 2014 13:16:56 +0000 [thread overview]
Message-ID: <53D10748.5000807@suse.de> (raw)
In-Reply-To: <1405922006-570-1-git-send-email-Bharat.Bhushan@freescale.com>
On 21.07.14 07:53, Bharat Bhushan wrote:
> SPRN_SPRG is used by debug interrupt handler, so this is required for
> debug support.
>
> Signed-off-by: Bharat Bhushan <Bharat.Bhushan@freescale.com>
> ---
> v1->v2
> - sprng9 is 64bit, not 32bit
Looks very reasonable, but is missing a ONE_REG interface to make the
register available to user space.
Alex
WARNING: multiple messages have this Message-ID (diff)
From: Alexander Graf <agraf@suse.de>
To: Bharat Bhushan <Bharat.Bhushan@freescale.com>, kvm-ppc@vger.kernel.org
Cc: kvm@vger.kernel.org, scottwood@freescale.com, stuart.yoder@freescale.com
Subject: Re: [PATCH v2] kvm: ppc: bookehv: Save restore SPRN_SPRG9 on guest entry exit
Date: Thu, 24 Jul 2014 15:16:56 +0200 [thread overview]
Message-ID: <53D10748.5000807@suse.de> (raw)
In-Reply-To: <1405922006-570-1-git-send-email-Bharat.Bhushan@freescale.com>
On 21.07.14 07:53, Bharat Bhushan wrote:
> SPRN_SPRG is used by debug interrupt handler, so this is required for
> debug support.
>
> Signed-off-by: Bharat Bhushan <Bharat.Bhushan@freescale.com>
> ---
> v1->v2
> - sprng9 is 64bit, not 32bit
Looks very reasonable, but is missing a ONE_REG interface to make the
register available to user space.
Alex
next prev parent reply other threads:[~2014-07-24 13:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-21 5:53 [PATCH v2] kvm: ppc: bookehv: Save restore SPRN_SPRG9 on guest entry exit Bharat Bhushan
2014-07-21 5:55 ` Bharat Bhushan
2014-07-24 13:16 ` Alexander Graf [this message]
2014-07-24 13:16 ` 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=53D10748.5000807@suse.de \
--to=agraf@suse.de \
--cc=Bharat.Bhushan@freescale.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=scottwood@freescale.com \
--cc=stuart.yoder@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.