From: "\"“tiejun.chen”\"" <tiejun.chen@windriver.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Scott Wood <scottwood@freescale.com>,
Alexander Graf <agraf@suse.de>
Cc: "kvm@vger.kernel.org list" <kvm@vger.kernel.org>,
kvm-ppc@vger.kernel.org
Subject: Re: [v2][PATCH 1/1] KVM: PPC: Book3E HV: call SOFT_DISABLE_INTS to sync the software state
Date: Thu, 15 Aug 2013 03:19:41 +0000 [thread overview]
Message-ID: <520C48CD.9050301@windriver.com> (raw)
In-Reply-To: <1376514097.4255.74.camel@pasglop>
On 08/15/2013 05:01 AM, Benjamin Herrenschmidt wrote:
> On Wed, 2013-08-14 at 14:34 -0500, Scott Wood wrote:
>> On Wed, 2013-08-14 at 13:56 +0200, Alexander Graf wrote:
>>> On 07.08.2013, at 04:05, Tiejun Chen wrote:
>>>
>>>> We enter with interrupts disabled in hardware, but we need to
>>>> call SOFT_DISABLE_INTS anyway to ensure that the software state
>>>> is kept in sync instead of calling hard_irq_disable() directly.
>>>>
>>>> Signed-off-by: Tiejun Chen <tiejun.chen@windriver.com>
>>>
>>> Scott, Ben, could you please ack?
>>
>> ACK, but it needs to be updated due to this patch that renames
>> SOFT_DISABLE_INTS:
>>
>> http://patchwork.ozlabs.org/patch/259337/
>
> Note that the latter was applied to powerpc -next already.
>
Thanks Ben and Scott.
Alex,
Should I resend an updated patch after you sync powerpc -next?
Tiejun
WARNING: multiple messages have this Message-ID (diff)
From: "\"“tiejun.chen”\"" <tiejun.chen@windriver.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Scott Wood <scottwood@freescale.com>,
Alexander Graf <agraf@suse.de>
Cc: "kvm@vger.kernel.org list" <kvm@vger.kernel.org>,
<kvm-ppc@vger.kernel.org>
Subject: Re: [v2][PATCH 1/1] KVM: PPC: Book3E HV: call SOFT_DISABLE_INTS to sync the software state
Date: Thu, 15 Aug 2013 11:19:41 +0800 [thread overview]
Message-ID: <520C48CD.9050301@windriver.com> (raw)
In-Reply-To: <1376514097.4255.74.camel@pasglop>
On 08/15/2013 05:01 AM, Benjamin Herrenschmidt wrote:
> On Wed, 2013-08-14 at 14:34 -0500, Scott Wood wrote:
>> On Wed, 2013-08-14 at 13:56 +0200, Alexander Graf wrote:
>>> On 07.08.2013, at 04:05, Tiejun Chen wrote:
>>>
>>>> We enter with interrupts disabled in hardware, but we need to
>>>> call SOFT_DISABLE_INTS anyway to ensure that the software state
>>>> is kept in sync instead of calling hard_irq_disable() directly.
>>>>
>>>> Signed-off-by: Tiejun Chen <tiejun.chen@windriver.com>
>>>
>>> Scott, Ben, could you please ack?
>>
>> ACK, but it needs to be updated due to this patch that renames
>> SOFT_DISABLE_INTS:
>>
>> http://patchwork.ozlabs.org/patch/259337/
>
> Note that the latter was applied to powerpc -next already.
>
Thanks Ben and Scott.
Alex,
Should I resend an updated patch after you sync powerpc -next?
Tiejun
next prev parent reply other threads:[~2013-08-15 3:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-07 2:05 [v2][PATCH 1/1] KVM: PPC: Book3E HV: call SOFT_DISABLE_INTS to sync the software state Tiejun Chen
2013-08-07 2:05 ` Tiejun Chen
2013-08-14 11:56 ` Alexander Graf
2013-08-14 11:56 ` Alexander Graf
2013-08-14 19:34 ` Scott Wood
2013-08-14 19:34 ` Scott Wood
2013-08-14 21:01 ` Benjamin Herrenschmidt
2013-08-14 21:01 ` Benjamin Herrenschmidt
2013-08-15 3:19 ` "“tiejun.chen”" [this message]
2013-08-15 3:19 ` "“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=520C48CD.9050301@windriver.com \
--to=tiejun.chen@windriver.com \
--cc=agraf@suse.de \
--cc=benh@kernel.crashing.org \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=scottwood@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.