From: Scott Wood <scottwood@freescale.com>
To: Alexander Graf <agraf@suse.de>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: <kvm-ppc@vger.kernel.org>, <kvm@vger.kernel.org>,
<linuxppc-dev@lists.ozlabs.org>
Subject: [PATCH v2 0/4] kvm/ppc: interrupt disabling fixes
Date: Thu, 9 May 2013 22:09:40 -0500 [thread overview]
Message-ID: <1368155384-11035-1-git-send-email-scottwood@freescale.com> (raw)
v2:
- Split into separate changes
- Rebase on top of (and fix a bug in) powerpc: Make hard_irq_disable()
do the right thing vs. irq tracing
- Move interrupt diasbling/enabling into kvmppc_handle_exit
Based on Ben's next branch.
Scott Wood (4):
powerpc: hard_irq_disable(): Call trace_hardirqs_off after disabling
kvm/ppc/booke64: Fix lazy ee handling in kvmppc_handle_exit()
kvm/ppc: Call trace_hardirqs_on before entry
kvm/ppc: IRQ disabling cleanup
arch/powerpc/include/asm/hw_irq.h | 5 +++--
arch/powerpc/include/asm/kvm_ppc.h | 17 ++++++++++++++---
arch/powerpc/kvm/book3s_pr.c | 16 +++++-----------
arch/powerpc/kvm/booke.c | 18 +++++++++---------
arch/powerpc/kvm/powerpc.c | 23 ++++++++---------------
5 files changed, 39 insertions(+), 40 deletions(-)
--
1.7.10.4
WARNING: multiple messages have this Message-ID (diff)
From: Scott Wood <scottwood@freescale.com>
To: Alexander Graf <agraf@suse.de>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@lists.ozlabs.org, kvm@vger.kernel.org,
kvm-ppc@vger.kernel.org
Subject: [PATCH v2 0/4] kvm/ppc: interrupt disabling fixes
Date: Thu, 9 May 2013 22:09:40 -0500 [thread overview]
Message-ID: <1368155384-11035-1-git-send-email-scottwood@freescale.com> (raw)
v2:
- Split into separate changes
- Rebase on top of (and fix a bug in) powerpc: Make hard_irq_disable()
do the right thing vs. irq tracing
- Move interrupt diasbling/enabling into kvmppc_handle_exit
Based on Ben's next branch.
Scott Wood (4):
powerpc: hard_irq_disable(): Call trace_hardirqs_off after disabling
kvm/ppc/booke64: Fix lazy ee handling in kvmppc_handle_exit()
kvm/ppc: Call trace_hardirqs_on before entry
kvm/ppc: IRQ disabling cleanup
arch/powerpc/include/asm/hw_irq.h | 5 +++--
arch/powerpc/include/asm/kvm_ppc.h | 17 ++++++++++++++---
arch/powerpc/kvm/book3s_pr.c | 16 +++++-----------
arch/powerpc/kvm/booke.c | 18 +++++++++---------
arch/powerpc/kvm/powerpc.c | 23 ++++++++---------------
5 files changed, 39 insertions(+), 40 deletions(-)
--
1.7.10.4
WARNING: multiple messages have this Message-ID (diff)
From: Scott Wood <scottwood@freescale.com>
To: Alexander Graf <agraf@suse.de>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: kvm-ppc@vger.kernel.org, kvm@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org
Subject: [PATCH v2 0/4] kvm/ppc: interrupt disabling fixes
Date: Fri, 10 May 2013 03:09:40 +0000 [thread overview]
Message-ID: <1368155384-11035-1-git-send-email-scottwood@freescale.com> (raw)
v2:
- Split into separate changes
- Rebase on top of (and fix a bug in) powerpc: Make hard_irq_disable()
do the right thing vs. irq tracing
- Move interrupt diasbling/enabling into kvmppc_handle_exit
Based on Ben's next branch.
Scott Wood (4):
powerpc: hard_irq_disable(): Call trace_hardirqs_off after disabling
kvm/ppc/booke64: Fix lazy ee handling in kvmppc_handle_exit()
kvm/ppc: Call trace_hardirqs_on before entry
kvm/ppc: IRQ disabling cleanup
arch/powerpc/include/asm/hw_irq.h | 5 +++--
arch/powerpc/include/asm/kvm_ppc.h | 17 ++++++++++++++---
arch/powerpc/kvm/book3s_pr.c | 16 +++++-----------
arch/powerpc/kvm/booke.c | 18 +++++++++---------
arch/powerpc/kvm/powerpc.c | 23 ++++++++---------------
5 files changed, 39 insertions(+), 40 deletions(-)
--
1.7.10.4
next reply other threads:[~2013-05-10 3:09 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-10 3:09 Scott Wood [this message]
2013-05-10 3:09 ` [PATCH v2 0/4] kvm/ppc: interrupt disabling fixes Scott Wood
2013-05-10 3:09 ` Scott Wood
2013-05-10 3:09 ` [PATCH v2 1/4] powerpc: hard_irq_disable(): Call trace_hardirqs_off after disabling Scott Wood
2013-05-10 3:09 ` Scott Wood
2013-05-10 3:09 ` Scott Wood
2013-05-10 7:00 ` Benjamin Herrenschmidt
2013-05-10 7:00 ` Benjamin Herrenschmidt
2013-05-10 7:00 ` Benjamin Herrenschmidt
2013-05-10 3:09 ` [PATCH v2 2/4] kvm/ppc/booke64: Fix lazy ee handling in kvmppc_handle_exit() Scott Wood
2013-05-10 3:09 ` Scott Wood
2013-05-10 3:09 ` Scott Wood
2013-05-10 5:01 ` Bhushan Bharat-R65777
2013-05-10 5:01 ` Bhushan Bharat-R65777
2013-05-10 22:43 ` Scott Wood
2013-05-10 22:43 ` Scott Wood
2013-05-10 22:43 ` Scott Wood
2013-05-10 3:09 ` [PATCH v2 3/4] kvm/ppc: Call trace_hardirqs_on before entry Scott Wood
2013-05-10 3:09 ` Scott Wood
2013-05-10 3:09 ` Scott Wood
2013-05-10 3:34 ` Bhushan Bharat-R65777
2013-05-10 3:34 ` Bhushan Bharat-R65777
2013-05-10 4:40 ` tiejun.chen
2013-05-10 4:40 ` tiejun.chen
2013-05-10 4:40 ` tiejun.chen
2013-05-10 22:47 ` Scott Wood
2013-05-10 22:47 ` Scott Wood
2013-05-10 3:09 ` [PATCH v2 4/4] kvm/ppc: IRQ disabling cleanup Scott Wood
2013-05-10 3:09 ` Scott Wood
2013-05-10 3:09 ` Scott Wood
2013-05-10 5:01 ` Bhushan Bharat-R65777
2013-05-10 5:01 ` Bhushan Bharat-R65777
2013-05-10 5:31 ` tiejun.chen
2013-05-10 5:31 ` tiejun.chen
2013-05-10 5:31 ` tiejun.chen
2013-05-10 22:53 ` Scott Wood
2013-05-10 22:53 ` Scott Wood
2013-05-10 22:53 ` Scott Wood
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=1368155384-11035-1-git-send-email-scottwood@freescale.com \
--to=scottwood@freescale.com \
--cc=agraf@suse.de \
--cc=benh@kernel.crashing.org \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.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 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.