From: Auger Eric <eric.auger@redhat.com>
To: Sinan Kaya <okaya@codeaurora.org>,
kvm@vger.kernel.org, timur@codeaurora.org, cov@codeaurora.org,
jcm@redhat.com, alex.williamson@redhat.com
Cc: linux-acpi@vger.kernel.org, agross@codeaurora.org,
linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH V8 0/9] vfio, platform: add ACPI support
Date: Thu, 23 Jun 2016 09:58:38 +0200 [thread overview]
Message-ID: <44afaabd-8393-fa97-ab61-664cd169bd9f@redhat.com> (raw)
In-Reply-To: <1466437879-32182-1-git-send-email-okaya@codeaurora.org>
Hi Sinan,
On 20/06/2016 17:51, Sinan Kaya wrote:
> The current code only supports the device tree based platforms.
> The code checks for the presence of a reset driver and calls the reset
> function pointer by looking up the reset driver as a module.
>
> ACPI defines _RST method to perform device level reset. After the _RST
> method is executed, the OS can resume using the device.
>
> The patchset is moving the device tree specific pieces out of the code
> to common functions so that ACPI support is added without impacting the
> rest of the code.
>
> During probe, the ACPI HID of the object will be saved and will be used to
> determine if this is an ACPI capable platform or not. If acpihid is NULL
> then, device tree functions are called.
>
> In addition to plumbing ACPI support, reset functionality is now a
> requirement by default.
>
> The code was allowing platform devices to be used without a supporting
> VFIO reset driver. The hardware can be left in some inconsistent state
> after a guest machine abort.
>
> The reset driver will put the hardware back to safe state and disable
> interrupts before returning the control back to the host machine.
>
> Adding a new reset_required kernel module option to AMBA and platform
> VFIO drivers with a default value of true.
>
> New requirements are:
> 1. A reset function needs to be implemented by the corresponding driver
> via DT/ACPI.
> 2. The reset function needs to be discovered via DT/ACPI.
>
> The probe of the driver will fail if any of the above conditions are
> not satisfied.
>
> Changes from V7:
> 1. Move the reset function test before IOMMU group set up so that we can
> clean up properly when reset function is not found.
> 2. Correct the _RST function call. _RST method does not return any value.
> We were calling acpi_evaluate_integer. The correct API needs to be
> acpi_evaluate_object.
>
> Sinan Kaya (9):
> vfio: platform: rename reset function
> vfio: platform: move reset call to a common function
> vfio: platform: determine reset capability
> vfio: platform: add support for ACPI probe
> vfio: platform: add extra debug info argument to call reset
> vfio: platform: call _RST method when using ACPI
> vfio, platform: make reset driver a requirement by default
> vfio: platform: check reset call return code during open
> vfio: platform: check reset call return code during release
>
> drivers/vfio/platform/vfio_amba.c | 5 +
> drivers/vfio/platform/vfio_platform.c | 5 +
> drivers/vfio/platform/vfio_platform_common.c | 197 +++++++++++++++++++++-----
> drivers/vfio/platform/vfio_platform_private.h | 8 +-
> 4 files changed, 177 insertions(+), 38 deletions(-)
>
I tested with device tree and I did not find any issue:
Tested-by: Eric Auger <eric.auger@redhat.com>
For the whole series:
Reviewed-by: Eric Auger <eric.auger@redhat.com>
Please note this will collide with "[PATCH V3] vfio: platform: support
No-IOMMU mode" (s/iommu_group_put/vfio_iommu_group_put)
Best Regards
Eric
next prev parent reply other threads:[~2016-06-23 7:58 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-20 15:51 [PATCH V8 0/9] vfio, platform: add ACPI support Sinan Kaya
2016-06-20 15:51 ` [PATCH V8 1/9] vfio: platform: rename reset function Sinan Kaya
2016-06-20 15:51 ` [PATCH V8 2/9] vfio: platform: move reset call to a common function Sinan Kaya
2016-06-20 15:51 ` [PATCH V8 3/9] vfio: platform: determine reset capability Sinan Kaya
2016-06-20 15:51 ` [PATCH V8 4/9] vfio: platform: add support for ACPI probe Sinan Kaya
2016-06-23 18:34 ` Alex Williamson
2016-07-13 19:36 ` Sinan Kaya
2016-07-13 20:09 ` Alex Williamson
2016-07-13 21:01 ` Sinan Kaya
2016-06-20 15:51 ` [PATCH V8 5/9] vfio: platform: add extra debug info argument to call reset Sinan Kaya
2016-06-20 15:51 ` [PATCH V8 6/9] vfio: platform: call _RST method when using ACPI Sinan Kaya
2016-06-20 15:51 ` [PATCH V8 7/9] vfio, platform: make reset driver a requirement by default Sinan Kaya
2016-06-23 18:59 ` Alex Williamson
2016-07-13 20:12 ` Sinan Kaya
2016-07-13 20:55 ` Alex Williamson
2016-07-13 21:34 ` Sinan Kaya
2016-07-13 20:48 ` Sinan Kaya
2016-07-13 21:18 ` Alex Williamson
2016-06-20 15:51 ` [PATCH V8 8/9] vfio: platform: check reset call return code during open Sinan Kaya
2016-06-20 15:51 ` [PATCH V8 9/9] vfio: platform: check reset call return code during release Sinan Kaya
2016-06-23 7:58 ` Auger Eric [this message]
2016-06-23 15:03 ` [PATCH V8 0/9] vfio, platform: add ACPI support Sinan Kaya
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=44afaabd-8393-fa97-ab61-664cd169bd9f@redhat.com \
--to=eric.auger@redhat.com \
--cc=agross@codeaurora.org \
--cc=alex.williamson@redhat.com \
--cc=cov@codeaurora.org \
--cc=jcm@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=okaya@codeaurora.org \
--cc=timur@codeaurora.org \
/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).