From: alex.williamson@redhat.com (Alex Williamson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V11 0/9] vfio, platform: add ACPI support
Date: Tue, 19 Jul 2016 15:50:25 -0600 [thread overview]
Message-ID: <20160719155025.7b7c1e32@t450s.home> (raw)
In-Reply-To: <1468933309-19735-1-git-send-email-okaya@codeaurora.org>
On Tue, 19 Jul 2016 09:01:40 -0400
Sinan Kaya <okaya@codeaurora.org> 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 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 V10:
> 1. Get rid of redundant if check in the acpi_probe since we are now using
> WARN_ON.
> 2. Change the error code order according to Alex's recommendation.
>
> 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 | 1 +
> drivers/vfio/platform/vfio_platform.c | 5 +
> drivers/vfio/platform/vfio_platform_common.c | 192 +++++++++++++++++++++-----
> drivers/vfio/platform/vfio_platform_private.h | 9 +-
> 4 files changed, 173 insertions(+), 34 deletions(-)
>
Applied to next branch for v4.8. Thanks,
Alex
prev parent reply other threads:[~2016-07-19 21:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-19 13:01 [PATCH V11 0/9] vfio, platform: add ACPI support Sinan Kaya
2016-07-19 13:01 ` [PATCH V11 1/9] vfio: platform: rename reset function Sinan Kaya
2016-07-19 13:01 ` [PATCH V11 2/9] vfio: platform: move reset call to a common function Sinan Kaya
2016-07-19 13:01 ` [PATCH V11 3/9] vfio: platform: determine reset capability Sinan Kaya
2016-07-19 13:01 ` [PATCH V11 4/9] vfio: platform: add support for ACPI probe Sinan Kaya
2016-07-19 13:01 ` [PATCH V11 5/9] vfio: platform: add extra debug info argument to call reset Sinan Kaya
2016-07-19 13:01 ` [PATCH V11 6/9] vfio: platform: call _RST method when using ACPI Sinan Kaya
2016-07-19 13:01 ` [PATCH V11 7/9] vfio, platform: make reset driver a requirement by default Sinan Kaya
2016-07-19 13:01 ` [PATCH V11 8/9] vfio: platform: check reset call return code during open Sinan Kaya
2016-07-19 13:01 ` [PATCH V11 9/9] vfio: platform: check reset call return code during release Sinan Kaya
2016-07-19 21:50 ` Alex Williamson [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=20160719155025.7b7c1e32@t450s.home \
--to=alex.williamson@redhat.com \
--cc=linux-arm-kernel@lists.infradead.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).