linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: Greg Kurz <groug@kaod.org>,
	Michael Ellerman <patch-notifications@ellerman.id.au>
Cc: lvivier@redhat.com, linuxppc-dev@lists.ozlabs.org,
	"Cédric Le Goater" <clg@kaod.org>,
	"David Gibson" <david@gibson.dropbear.id.au>
Subject: Re: [PATCH] powerpc/xive: skip ioremap() of ESB pages for LSI interrupts
Date: Thu, 05 Dec 2019 08:18:43 +1100	[thread overview]
Message-ID: <87k17beqmk.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <20191204154220.7affb01f@bahia.w3ibm.bluemix.net>

Greg Kurz <groug@kaod.org> writes:
> On Thu,  5 Dec 2019 00:30:56 +1100 (AEDT)
> Michael Ellerman <patch-notifications@ellerman.id.au> wrote:
>> On Tue, 2019-12-03 at 16:36:42 UTC, =?UTF-8?q?C=C3=A9dric=20Le=20Goater?= wrote:
>> > The PCI INTx interrupts and other LSI interrupts are handled differently
>> > under a sPAPR platform. When the interrupt source characteristics are
>> > queried, the hypervisor returns an H_INT_ESB flag to inform the OS
>> > that it should be using the H_INT_ESB hcall for interrupt management
>> > and not loads and stores on the interrupt ESB pages.
...
>> > 
>> > Cc: stable@vger.kernel.org # v4.14+
>> > Fixes: bed81ee181dd ("powerpc/xive: introduce H_INT_ESB hcall")
>> > Signed-off-by: Cédric Le Goater <clg@kaod.org>
>> 
>> Applied to powerpc fixes, thanks.
>> 
>> https://git.kernel.org/powerpc/c/b67a95f2abff0c34e5667c15ab8900de73d8d087
>> 
>
> My R-b tag is missing... I guess I didn't review it quick enough :)

Yeah sorry, your tag arrived after I'd applied it but before I'd pushed
it out.

Thanks for reviewing it anyway. You can redeem lost R-b tags for a free
beer at any conference we're both attending :)

cheers

      reply	other threads:[~2019-12-04 21:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-03 16:36 [PATCH] powerpc/xive: skip ioremap() of ESB pages for LSI interrupts Cédric Le Goater
2019-12-04 10:03 ` Greg Kurz
2019-12-04 13:30 ` Michael Ellerman
2019-12-04 14:42   ` Greg Kurz
2019-12-04 21:18     ` Michael Ellerman [this message]

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=87k17beqmk.fsf@mpe.ellerman.id.au \
    --to=mpe@ellerman.id.au \
    --cc=clg@kaod.org \
    --cc=david@gibson.dropbear.id.au \
    --cc=groug@kaod.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=lvivier@redhat.com \
    --cc=patch-notifications@ellerman.id.au \
    /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).