From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Kevin Hao <haokexin@gmail.com>
Cc: Scott Wood <scottwood@freescale.com>,
"tiejun.chen" <tiejun.chen@windriver.com>,
Bhushan Bharat-R65777 <R65777@freescale.com>,
Caraman Mihai Claudiu-B02008 <B02008@freescale.com>,
Wood Scott-B07421 <B07421@freescale.com>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"agraf@suse.de" <agraf@suse.de>,
"kvm-ppc@vger.kernel.org" <kvm-ppc@vger.kernel.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [RFC][KVM][PATCH 1/1] kvm:ppc:booke-64: soft-disable interrupts
Date: Fri, 10 May 2013 21:49:40 +0000 [thread overview]
Message-ID: <1368222580.4524.52.camel@pasglop> (raw)
In-Reply-To: <20130510141213.GA31597@pek-khao-d1.corp.ad.wrs.com>
On Fri, 2013-05-10 at 22:12 +0800, Kevin Hao wrote:
> So I would assume you will not pick up these two patches, right?
> http://patchwork.ozlabs.org/patch/235530/
> http://patchwork.ozlabs.org/patch/235532/
>
> Anyway it is more easier to enable the external proxy by using this method.
> But if you insist, I can respin a patch to use the method you suggested
> since it will definitely reduce the window where the irq is hard disabled.
I would keep the EE_EDGE bit definition. I have no objection to a gradual
approach however for the other one where we apply it as is now to enable
coreint while you do a rework to make it better :-)
Cheers,
Ben.
next prev parent reply other threads:[~2013-05-10 21:49 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1368134856.654.11@snotra>
2013-05-09 22:07 ` [RFC][KVM][PATCH 1/1] kvm:ppc:booke-64: soft-disable interrupts Benjamin Herrenschmidt
2013-05-10 14:12 ` Kevin Hao
2013-05-10 21:49 ` Benjamin Herrenschmidt [this message]
2013-05-10 21:50 ` Benjamin Herrenschmidt
[not found] <1367884257.3398.9@snotra>
2013-05-07 1:56 ` tiejun.chen
[not found] ` <1367892390.3398.12@snotra>
2013-05-07 2:43 ` tiejun.chen
[not found] ` <300B73AA675FCE4A93EB4FC1D42459FF3F00D0@039-SN2MPN1-013.039d.mgd.msft.net>
[not found] ` <6A3DF150A5B70D4F9B66A25E3F7C888D0700E50E@039-SN2MPN1-011.039d.mgd.msft.net>
2013-05-09 7:47 ` tiejun.chen
[not found] ` <6A3DF150A5B70D4F9B66A25E3F7C888D0700E563@039-SN2MPN1-011.039d.mgd.msft.net>
2013-05-09 8:04 ` tiejun.chen
2013-05-09 8:08 ` Kevin Hao
[not found] ` <6A3DF150A5B70D4F9B66A25E3F7C888D0700E5F5@039-SN2MPN1-011.039d.mgd.msft.net>
2013-05-09 8:17 ` tiejun.chen
2013-05-09 8:21 ` Kevin Hao
2013-05-09 12:26 ` Benjamin Herrenschmidt
[not found] ` <6A3DF150A5B70D4F9B66A25E3F7C888D0700E64A@039-SN2MPN1-011.039d.mgd.msft.net>
2013-05-09 9:44 ` tiejun.chen
[not found] ` <6A3DF150A5B70D4F9B66A25E3F7C888D0700E85D@039-SN2MPN1-011.039d.mgd.msft.net>
2013-05-09 10:18 ` tiejun.chen
[not found] ` <6A3DF150A5B70D4F9B66A25E3F7C888D0700E9C1@039-SN2MPN1-011.039d.mgd.msft.net>
2013-05-09 11:35 ` tiejun.chen
2013-05-09 12:37 ` Benjamin Herrenschmidt
2013-05-09 13:28 ` David Laight
2013-05-09 22:01 ` Benjamin Herrenschmidt
2013-05-09 14:13 ` Chen, Tiejun
2013-05-06 3:10 Tiejun Chen
2013-05-06 3:13 ` tiejun.chen
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=1368222580.4524.52.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=B02008@freescale.com \
--cc=B07421@freescale.com \
--cc=R65777@freescale.com \
--cc=agraf@suse.de \
--cc=haokexin@gmail.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=scottwood@freescale.com \
--cc=tiejun.chen@windriver.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox