From: "Laszlo Ersek" <lersek@redhat.com>
To: devel@edk2.groups.io, liran.alon@oracle.com
Cc: nikita.leshchenko@oracle.com, aaron.young@oracle.com,
jordan.l.justen@intel.com, ard.biesheuvel@linaro.org
Subject: Re: [edk2-devel] [PATCH 05/17] OvmfPkg/PvScsiDxe: Install stubbed EXT_SCSI_PASS_THRU
Date: Tue, 24 Mar 2020 13:47:34 +0100 [thread overview]
Message-ID: <857644e5-4345-29d1-1015-2c19142f5203@redhat.com> (raw)
In-Reply-To: <6e9f1702-5c10-6b84-6497-a32ee119acd1@redhat.com>
On 03/24/20 13:27, Laszlo Ersek wrote:
> On 03/16/20 16:01, Liran Alon wrote:
>> Support dynamic insertion and removal of the protocol.
>>
>> Ref: https://bugzilla.tianocore.org/show_bug.cgi?id=2567
>> Reviewed-by: Nikita Leshenko <nikita.leshchenko@oracle.com>
>> Signed-off-by: Liran Alon <liran.alon@oracle.com>
>> ---
>> OvmfPkg/PvScsiDxe/PvScsi.c | 209 ++++++++++++++++++++++++++++++++++-
>> OvmfPkg/PvScsiDxe/PvScsi.h | 29 +++++
>> OvmfPkg/PvScsiDxe/PvScsi.inf | 5 +-
>> 3 files changed, 240 insertions(+), 3 deletions(-)
>> create mode 100644 OvmfPkg/PvScsiDxe/PvScsi.h
>>
>> diff --git a/OvmfPkg/PvScsiDxe/PvScsi.c b/OvmfPkg/PvScsiDxe/PvScsi.c
>> index f1fffe962233..46b430a34a57 100644
>> --- a/OvmfPkg/PvScsiDxe/PvScsi.c
>> +++ b/OvmfPkg/PvScsiDxe/PvScsi.c
>> @@ -11,16 +11,155 @@
>>
>> #include <IndustryStandard/Pci.h>
>> #include <IndustryStandard/PvScsi.h>
>> +#include <Library/MemoryAllocationLib.h>
>> #include <Library/UefiBootServicesTableLib.h>
>> #include <Library/UefiLib.h>
>> #include <Protocol/PciIo.h>
>>
>> +#include "PvScsi.h"
>> +
>> //
>> // Higher versions will be used before lower, 0x10-0xffffffef is the version
>> // range for IVH (Indie Hardware Vendors)
>> //
>> #define PVSCSI_BINDING_VERSION 0x10
>>
>> +//
>> +// Ext SCSI Pass Thru
>> +//
>> +
>> +STATIC
>> +EFI_STATUS
>> +EFIAPI
>> +PvScsiPassThru (
>> + IN EFI_EXT_SCSI_PASS_THRU_PROTOCOL *This,
>> + IN UINT8 *Target,
>> + IN UINT64 Lun,
>> + IN OUT EFI_EXT_SCSI_PASS_THRU_SCSI_REQUEST_PACKET *Packet,
>> + IN EFI_EVENT Event OPTIONAL
>> + )
>> +{
>> + return EFI_UNSUPPORTED;
>> +}
>> +
>> +STATIC
>> +EFI_STATUS
>> +EFIAPI
>> +PvScsiGetNextTargetLun (
>> + IN EFI_EXT_SCSI_PASS_THRU_PROTOCOL *This,
>> + IN OUT UINT8 **Target,
>> + IN OUT UINT64 *Lun
>> + )
>> +{
>> + return EFI_UNSUPPORTED;
>> +}
>> +
>> +STATIC
>> +EFI_STATUS
>> +EFIAPI
>> +PvScsiBuildDevicePath (
>> + IN EFI_EXT_SCSI_PASS_THRU_PROTOCOL *This,
>> + IN UINT8 *Target,
>> + IN UINT64 Lun,
>> + IN OUT EFI_DEVICE_PATH_PROTOCOL **DevicePath
>> + )
>> +{
>> + return EFI_UNSUPPORTED;
>> +}
>> +
>> +STATIC
>> +EFI_STATUS
>> +EFIAPI
>> +PvScsiGetTargetLun (
>> + IN EFI_EXT_SCSI_PASS_THRU_PROTOCOL *This,
>> + IN EFI_DEVICE_PATH_PROTOCOL *DevicePath,
>> + OUT UINT8 **Target,
>> + OUT UINT64 *Lun
>> + )
>> +{
>> + return EFI_UNSUPPORTED;
>> +}
>> +
>> +STATIC
>> +EFI_STATUS
>> +EFIAPI
>> +PvScsiResetChannel (
>> + IN EFI_EXT_SCSI_PASS_THRU_PROTOCOL *This
>> + )
>> +{
>> + return EFI_UNSUPPORTED;
>> +}
>> +
>> +STATIC
>> +EFI_STATUS
>> +EFIAPI
>> +PvScsiResetTargetLun (
>> + IN EFI_EXT_SCSI_PASS_THRU_PROTOCOL *This,
>> + IN UINT8 *Target,
>> + IN UINT64 Lun
>> + )
>> +{
>> + return EFI_UNSUPPORTED;
>> +}
>> +
>> +STATIC
>> +EFI_STATUS
>> +EFIAPI
>> +PvScsiGetNextTarget (
>> + IN EFI_EXT_SCSI_PASS_THRU_PROTOCOL *This,
>> + IN OUT UINT8 **Target
>> + )
>> +{
>> + return EFI_UNSUPPORTED;
>> +}
>> +
>> +STATIC
>> +EFI_STATUS
>> +PvScsiInit (
>> + IN OUT PVSCSI_DEV *Dev
>> + )
>> +{
>> + //
>> + // Populate the exported interface's attributes
>> + //
>> + Dev->PassThru.Mode = &Dev->PassThruMode;
>> + Dev->PassThru.PassThru = &PvScsiPassThru;
>> + Dev->PassThru.GetNextTargetLun = &PvScsiGetNextTargetLun;
>> + Dev->PassThru.BuildDevicePath = &PvScsiBuildDevicePath;
>> + Dev->PassThru.GetTargetLun = &PvScsiGetTargetLun;
>> + Dev->PassThru.ResetChannel = &PvScsiResetChannel;
>> + Dev->PassThru.ResetTargetLun = &PvScsiResetTargetLun;
>> + Dev->PassThru.GetNextTarget = &PvScsiGetNextTarget;
>> +
>> + //
>> + // AdapterId is a target for which no handle will be created during bus scan.
>> + // Prevent any conflict with real devices.
>> + //
>> + Dev->PassThruMode.AdapterId = MAX_UINT32;
>> +
>> + //
>> + // Set both physical and logical attributes for non-RAID SCSI channel
>> + //
>> + Dev->PassThruMode.Attributes = EFI_EXT_SCSI_PASS_THRU_ATTRIBUTES_PHYSICAL |
>> + EFI_EXT_SCSI_PASS_THRU_ATTRIBUTES_LOGICAL;
>> +
>> + //
>> + // No restriction on transfer buffer alignment
>> + //
>> + Dev->PassThruMode.IoAlign = 0;
>> +
>> + return EFI_SUCCESS;
>> +}
>> +
>> +STATIC
>> +VOID
>> +PvScsiUninit (
>> + IN OUT PVSCSI_DEV *Dev
>> + )
>> +{
>> + // Currently nothing to do here
>> +}
>> +
>> //
>> // Driver Binding
>> //
>> @@ -89,7 +228,42 @@ PvScsiDriverBindingStart (
>> IN EFI_DEVICE_PATH_PROTOCOL *RemainingDevicePath OPTIONAL
>> )
>> {
>> - return EFI_UNSUPPORTED;
>> + PVSCSI_DEV *Dev;
>> + EFI_STATUS Status;
>> +
>> + Dev = (PVSCSI_DEV *) AllocateZeroPool (sizeof (*Dev));
>> + if (Dev == NULL) {
>> + return EFI_OUT_OF_RESOURCES;
>> + }
>> +
>> + Status = PvScsiInit (Dev);
>> + if (EFI_ERROR (Status)) {
>> + goto FreePvScsi;
>> + }
>> +
>> + //
>> + // Setup complete, attempt to export the driver instance's PassThru interface
>> + //
>> + Dev->Signature = PVSCSI_SIG;
>> + Status = gBS->InstallProtocolInterface (
>> + &ControllerHandle,
>> + &gEfiExtScsiPassThruProtocolGuid,
>> + EFI_NATIVE_INTERFACE,
>> + &Dev->PassThru
>> + );
>> + if (EFI_ERROR (Status)) {
>> + goto UninitDev;
>> + }
>> +
>> + return EFI_SUCCESS;
>> +
>> +UninitDev:
>> + PvScsiUninit (Dev);
>> +
>> +FreePvScsi:
>> + FreePool (Dev);
>> +
>> + return Status;
>> }
>>
>> STATIC
>> @@ -102,7 +276,38 @@ PvScsiDriverBindingStop (
>> IN EFI_HANDLE *ChildHandleBuffer
>> )
>> {
>> - return EFI_UNSUPPORTED;
>> + EFI_STATUS Status;
>> + EFI_EXT_SCSI_PASS_THRU_PROTOCOL *PassThru;
>> + PVSCSI_DEV *Dev;
>> +
>> + Status = gBS->OpenProtocol (
>> + ControllerHandle,
>> + &gEfiExtScsiPassThruProtocolGuid,
>> + (VOID **)&PassThru,
>> + This->DriverBindingHandle,
>> + ControllerHandle,
>> + EFI_OPEN_PROTOCOL_GET_PROTOCOL // Lookup only
>> + );
>> + if (EFI_ERROR (Status)) {
>> + return Status;
>> + }
>> +
>> + Dev = PVSCSI_FROM_PASS_THRU (PassThru);
>> +
>> + Status = gBS->UninstallProtocolInterface (
>> + ControllerHandle,
>> + &gEfiExtScsiPassThruProtocolGuid,
>> + &Dev->PassThru
>> + );
>> + if (EFI_ERROR (Status)) {
>> + return Status;
>> + }
>> +
>> + PvScsiUninit (Dev);
>> +
>> + FreePool (Dev);
>> +
>> + return EFI_SUCCESS;
>> }
>>
>> STATIC
>> diff --git a/OvmfPkg/PvScsiDxe/PvScsi.h b/OvmfPkg/PvScsiDxe/PvScsi.h
>> new file mode 100644
>> index 000000000000..3940b4c20019
>> --- /dev/null
>> +++ b/OvmfPkg/PvScsiDxe/PvScsi.h
>> @@ -0,0 +1,29 @@
>> +/** @file
>> +
>> + Internal definitions for the PVSCSI driver, which produces Extended SCSI
>> + Pass Thru Protocol instances for pvscsi devices.
>> +
>> + Copyright (C) 2020, Oracle and/or its affiliates.
>> +
>> + SPDX-License-Identifier: BSD-2-Clause-Patent
>> +
>> +**/
>> +
>> +#ifndef __PVSCSI_DXE_H_
>> +#define __PVSCSI_DXE_H_
>> +
>> +#include <Library/DebugLib.h>
>> +#include <Protocol/ScsiPassThruExt.h>
>> +
>> +#define PVSCSI_SIG SIGNATURE_32 ('P', 'S', 'C', 'S')
>> +
>> +typedef struct {
>> + UINT32 Signature;
>> + EFI_EXT_SCSI_PASS_THRU_PROTOCOL PassThru;
>> + EFI_EXT_SCSI_PASS_THRU_MODE PassThruMode;
>> +} PVSCSI_DEV;
>> +
>> +#define PVSCSI_FROM_PASS_THRU(PassThruPointer) \
>> + CR (PassThruPointer, PVSCSI_DEV, PassThru, PVSCSI_SIG)
>> +
>> +#endif // __PVSCSI_DXE_H_
>> diff --git a/OvmfPkg/PvScsiDxe/PvScsi.inf b/OvmfPkg/PvScsiDxe/PvScsi.inf
>> index c1f0663832ed..3a8b07872ba3 100644
>> --- a/OvmfPkg/PvScsiDxe/PvScsi.inf
>> +++ b/OvmfPkg/PvScsiDxe/PvScsi.inf
>> @@ -25,9 +25,12 @@
>> OvmfPkg/OvmfPkg.dec
>>
>> [LibraryClasses]
>> + DebugLib
>> + MemoryAllocationLib
>> UefiBootServicesTableLib
>> UefiDriverEntryPoint
>> UefiLib
>>
>> [Protocols]
>> - gEfiPciIoProtocolGuid ## TO_START
>> + gEfiPciIoProtocolGuid ## TO_START
>> + gEfiExtScsiPassThruProtocolGuid ## BY_START
>>
>
> (1) In the [Sources] section of the INF file, please list the new header
> file ("PvScsi.h").
(2) Please keep the list of protocols lexicographically sorted. (I
understand that you may have intended to place BY_START logically under
TO_START -- that looks simple enough initially, but with time it can get
messy. With normal sorting, there's never any doubt though.)
>
> With that:
>
> Reviewed-by: Laszlo Ersek <lersek@redhat.com>
This stands.
Thanks
Laszlo
next prev parent reply other threads:[~2020-03-24 12:47 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-16 15:00 [PATCH 00/17]: OvmfPkg: Support booting from VMware PVSCSI controller liran.alon
2020-03-16 15:00 ` [PATCH 01/17] OvmfPkg/PvScsiDxe: Create empty driver Liran Alon
2020-03-24 11:15 ` [edk2-devel] " Laszlo Ersek
2020-03-16 15:00 ` [PATCH 02/17] OvmfPkg/PvScsiDxe: Install DriverBinding protocol Liran Alon
2020-03-24 11:23 ` [edk2-devel] " Laszlo Ersek
2020-03-16 15:00 ` [PATCH 03/17] OvmfPkg/PvScsiDxe: Report name of driver Liran Alon
2020-03-24 11:29 ` [edk2-devel] " Laszlo Ersek
2020-03-16 15:01 ` [PATCH 04/17] OvmfPkg/PvScsiDxe: Probe PCI devices and look for PvScsi Liran Alon
2020-03-24 11:41 ` [edk2-devel] " Laszlo Ersek
2020-03-16 15:01 ` [PATCH 05/17] OvmfPkg/PvScsiDxe: Install stubbed EXT_SCSI_PASS_THRU Liran Alon
2020-03-24 12:27 ` [edk2-devel] " Laszlo Ersek
2020-03-24 12:47 ` Laszlo Ersek [this message]
2020-03-16 15:01 ` [PATCH 06/17] OvmfPkg/PvScsiDxe: Report the number of targets and LUNs Liran Alon
2020-03-24 13:12 ` [edk2-devel] " Laszlo Ersek
2020-03-16 15:01 ` [PATCH 07/17] OvmfPkg/PvScsiDxe: Translate Target & LUN to/from DevicePath Liran Alon
2020-03-24 13:36 ` [edk2-devel] " Laszlo Ersek
2020-03-16 15:01 ` [PATCH 08/17] OvmfPkg/PvScsiDxe: Open PciIo protocol for later use Liran Alon
2020-03-24 13:47 ` [edk2-devel] " Laszlo Ersek
2020-03-16 15:01 ` [PATCH 09/17] OvmfPkg/PvScsiDxe: Backup/Restore PCI attributes on Init/UnInit Liran Alon
2020-03-24 15:14 ` [edk2-devel] " Laszlo Ersek
2020-03-24 15:35 ` Liran Alon
2020-03-25 1:48 ` Laszlo Ersek
2020-03-25 10:32 ` Liran Alon
2020-03-16 15:01 ` [PATCH 10/17] OvmfPkg/PvScsiDxe: Enable IOSpace & Bus-Mastering in PCI attributes Liran Alon
2020-03-24 15:22 ` [edk2-devel] " Laszlo Ersek
2020-03-16 15:01 ` [PATCH 11/17] OvmfPkg/PvScsiDxe: Define device interface structures and constants Liran Alon
2020-03-24 15:35 ` [edk2-devel] " Laszlo Ersek
2020-03-24 16:34 ` Laszlo Ersek
2020-03-16 15:01 ` [PATCH 12/17] OvmfPkg/PvScsiDxe: Reset adapter on init Liran Alon
2020-03-24 16:00 ` [edk2-devel] " Laszlo Ersek
2020-03-25 1:11 ` Liran Alon
2020-03-25 16:31 ` Laszlo Ersek
2020-03-25 16:40 ` Liran Alon
2020-03-25 17:13 ` Liran Alon
2020-03-27 12:55 ` Laszlo Ersek
2020-03-16 15:01 ` [PATCH 13/17] OvmfPkg/PvScsiDxe: Setup requests and completions rings Liran Alon
2020-03-24 16:11 ` [edk2-devel] " Laszlo Ersek
2020-03-16 15:01 ` [PATCH 14/17] OvmfPkg/PvScsiDxe: Introduce DMA communication buffer Liran Alon
2020-03-24 16:13 ` [edk2-devel] " Laszlo Ersek
2020-03-16 15:01 ` [PATCH 15/17] OvmfPkg/PvScsiDxe: Support sending SCSI request and receive response Liran Alon
2020-03-24 16:43 ` [edk2-devel] " Laszlo Ersek
2020-03-25 1:17 ` Liran Alon
2020-03-16 15:01 ` [PATCH 16/17] OvmfPkg/PvScsiDxe: Reset device on ExitBootServices() Liran Alon
2020-03-24 17:04 ` [edk2-devel] " Laszlo Ersek
2020-03-16 15:01 ` [PATCH 17/17] OvmfPkg/PvScsiDxe: Enable device 64-bit DMA addresses Liran Alon
2020-03-24 15:26 ` [edk2-devel] " Laszlo Ersek
2020-03-23 16:33 ` [edk2-devel] [PATCH 00/17]: OvmfPkg: Support booting from VMware PVSCSI controller Laszlo Ersek
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-list 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=857644e5-4345-29d1-1015-2c19142f5203@redhat.com \
--to=devel@edk2.groups.io \
/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