From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Michael Ellerman <mpe@ellerman.id.au>, Cédric Le Goater <clg@kaod.org>
Cc: Alexey Kardashevskiy <aik@ozlabs.ru>,
Oliver O'Halloran <oohall@gmail.com>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v2] powerpc/pci: unmap legacy INTx interrupts when a PHB is removed
Date: Thu, 17 Sep 2020 21:27:26 +1000 (AEST) [thread overview]
Message-ID: <160034201731.3339803.17760371950338467723.b4-ty@ellerman.id.au> (raw)
In-Reply-To: <20200807101854.844619-1-clg@kaod.org>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 793 bytes --]
On Fri, 7 Aug 2020 12:18:54 +0200, Cédric Le Goater wrote:
> When a passthrough IO adapter is removed from a pseries machine using
> hash MMU and the XIVE interrupt mode, the POWER hypervisor expects the
> guest OS to clear all page table entries related to the adapter. If
> some are still present, the RTAS call which isolates the PCI slot
> returns error 9001 "valid outstanding translations" and the removal of
> the IO adapter fails. This is because when the PHBs are scanned, Linux
> maps automatically the INTx interrupts in the Linux interrupt number
> space but these are never removed.
>
> [...]
Applied to powerpc/next.
[1/1] powerpc/pci: unmap legacy INTx interrupts when a PHB is removed
https://git.kernel.org/powerpc/c/3a3181e16fbde752007759f8759d25e0ff1fc425
cheers
next prev parent reply other threads:[~2020-09-17 12:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-07 10:18 [PATCH v2] powerpc/pci: unmap legacy INTx interrupts when a PHB is removed Cédric Le Goater
2020-09-09 6:16 ` Alexey Kardashevskiy
2020-09-17 11:27 ` Michael Ellerman [this message]
2020-09-23 0:33 ` Qian Cai
2020-09-23 7:06 ` Cédric Le Goater
2020-09-24 5:11 ` Alexey Kardashevskiy
2020-09-24 10:31 ` Cédric Le Goater
2020-10-13 19:33 ` Qian Cai
2020-10-13 23:42 ` Michael Ellerman
2020-10-14 2:55 ` Alexey Kardashevskiy
2020-11-02 14:39 ` Cédric Le Goater
2020-11-03 4:40 ` Oliver O'Halloran
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=160034201731.3339803.17760371950338467723.b4-ty@ellerman.id.au \
--to=patch-notifications@ellerman.id.au \
--cc=aik@ozlabs.ru \
--cc=clg@kaod.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=oohall@gmail.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;
as well as URLs for NNTP newsgroup(s).