From: Ganesh <ganeshgr@linux.ibm.com>
To: Jason Gunthorpe <jgg@ziepe.ca>
Cc: linuxppc-dev@lists.ozlabs.org, mahesh@linux.ibm.com
Subject: Re: [RFC 0/3] Asynchronous EEH recovery
Date: Thu, 15 Sep 2022 15:45:47 +0530 [thread overview]
Message-ID: <f49d73c7-6f80-53d5-9a54-43ea2ace860e@linux.ibm.com> (raw)
In-Reply-To: <YxFMJEWSfSBkcwyq@ziepe.ca>
[-- Attachment #1: Type: text/plain, Size: 635 bytes --]
On 9/2/22 05:49, Jason Gunthorpe wrote:
> On Tue, Aug 16, 2022 at 08:57:13AM +0530, Ganesh Goudar wrote:
>> Hi,
>>
>> EEH reocvery is currently serialized and these patches shorten
>> the time taken for EEH recovery by making the recovery to run
>> in parallel. The original author of these patches is Sam Bobroff,
>> I have rebased and tested these patches.
> How did you test this?
This is tested on SRIOV VFs.
>
> I understand that VFIO on 6.0 does not work at all on power?
>
> I am waiting for power maintainers to pick up this series to fix it:
>
> https://lore.kernel.org/kvm/20220714081822.3717693-1-aik@ozlabs.ru/
>
> Jason
[-- Attachment #2: Type: text/html, Size: 1328 bytes --]
next prev parent reply other threads:[~2022-09-15 22:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-16 3:27 [RFC 0/3] Asynchronous EEH recovery Ganesh Goudar
2022-08-16 3:27 ` [RFC 1/3] powerpc/eeh: Synchronization for safety Ganesh Goudar
2022-08-16 3:27 ` [RFC 2/3] powerpc/eeh: Provide a unique ID for each EEH recovery Ganesh Goudar
2022-08-16 3:27 ` [RFC 3/3] powerpc/eeh: Asynchronous recovery Ganesh Goudar
2022-08-17 7:16 ` [RFC 0/3] Asynchronous EEH recovery Oliver O'Halloran
2022-09-02 0:19 ` Jason Gunthorpe
2022-09-15 10:15 ` Ganesh [this message]
2023-01-25 14:04 ` Christophe Leroy
-- strict thread matches above, loose matches on Subject: below --
2023-06-13 1:43 Ganesh Goudar
2023-06-13 2:36 ` Oliver O'Halloran
2023-07-17 8:10 ` Ganesh G R
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=f49d73c7-6f80-53d5-9a54-43ea2ace860e@linux.ibm.com \
--to=ganeshgr@linux.ibm.com \
--cc=jgg@ziepe.ca \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mahesh@linux.ibm.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).