|
Re: [PATCH] .azurepipelines: Enable CI for OvmfPkg and EmulatorPkg
Ard,
I agree. How would we do this with AARCH64? I don't believe azure devops pipelines has a native AARCH64 platform available. I briefly looked over ArmVirtPkg but not sure where to start. OVMF
Ard,
I agree. How would we do this with AARCH64? I don't believe azure devops pipelines has a native AARCH64 platform available. I briefly looked over ArmVirtPkg but not sure where to start. OVMF
|
By
Sean
·
#56554
·
|
|
Re: [EXTERNAL] [edk2-devel] Information about the VMs used to do EDK2 CI?
This works on my MacBook Pro
$ getconf _NPROCESSORS_ONLN
8
The macOS centric way is this:
$ sysctl -n hw.logicalcpu
8
Thanks,
Andrew FIsh
This works on my MacBook Pro
$ getconf _NPROCESSORS_ONLN
8
The macOS centric way is this:
$ sysctl -n hw.logicalcpu
8
Thanks,
Andrew FIsh
|
By
Andrew Fish
·
#56553
·
|
|
Re: [PATCH] .azurepipelines: Enable CI for OvmfPkg and EmulatorPkg
<sean.brogan@...> wrote:
Hello Sean,
Thanks a lot for taking the time to work on this. IMO, having a CI
smoke test that boots, say, an X64 as well as a AARCH64 virtual
platform to
<sean.brogan@...> wrote:
Hello Sean,
Thanks a lot for taking the time to work on this. IMO, having a CI
smoke test that boots, say, an X64 as well as a AARCH64 virtual
platform to
|
By
Ard Biesheuvel
·
#56552
·
|
|
Re: [EXTERNAL] [edk2-devel] Information about the VMs used to do EDK2 CI?
Thanks
I opened a bug to get this tracked. https://bugzilla.tianocore.org/show_bug.cgi?id=2640
In that bug i link to a commit which does the above using python. It saves about 20 seconds for each
Thanks
I opened a bug to get this tracked. https://bugzilla.tianocore.org/show_bug.cgi?id=2640
In that bug i link to a commit which does the above using python. It saves about 20 seconds for each
|
By
Sean
·
#56551
·
|
|
[PATCH v3 17/17] OvmfPkg/PvScsiDxe: Enable device 64-bit DMA addresses
Enable PCI dual-address cycle attribute to signal device
supports 64-bit DMA addresses.
Ref: https://bugzilla.tianocore.org/show_bug.cgi?id=2567
Reviewed-by: Laszlo Ersek
Enable PCI dual-address cycle attribute to signal device
supports 64-bit DMA addresses.
Ref: https://bugzilla.tianocore.org/show_bug.cgi?id=2567
Reviewed-by: Laszlo Ersek
|
By
Liran Alon
·
#56550
·
|
|
[PATCH v3 16/17] OvmfPkg/PvScsiDxe: Reset device on ExitBootServices()
This causes the device to forget about the request/completion rings.
We allocated said rings in EfiBootServicesData type memory, and code
executing after ExitBootServices() is permitted to overwrite
This causes the device to forget about the request/completion rings.
We allocated said rings in EfiBootServicesData type memory, and code
executing after ExitBootServices() is permitted to overwrite
|
By
Liran Alon
·
#56549
·
|
|
[PATCH v3 15/17] OvmfPkg/PvScsiDxe: Support sending SCSI request and receive response
Implement EXT_SCSI_PASS_THRU.PassThru().
Machines should be able to boot after this commit.
Tested with Ubuntu 16.04 guest.
Ref: https://bugzilla.tianocore.org/show_bug.cgi?id=2567
Signed-off-by:
Implement EXT_SCSI_PASS_THRU.PassThru().
Machines should be able to boot after this commit.
Tested with Ubuntu 16.04 guest.
Ref: https://bugzilla.tianocore.org/show_bug.cgi?id=2567
Signed-off-by:
|
By
Liran Alon
·
#56548
·
|
|
[PATCH v3 14/17] OvmfPkg/PvScsiDxe: Introduce DMA communication buffer
In case device is constrained by IOMMU or guest is running under AMD SEV,
input/output buffers provided to device (DataBuffer and SenseData) needs
to be explicitly mapped to device by
In case device is constrained by IOMMU or guest is running under AMD SEV,
input/output buffers provided to device (DataBuffer and SenseData) needs
to be explicitly mapped to device by
|
By
Liran Alon
·
#56547
·
|
|
[PATCH v3 13/17] OvmfPkg/PvScsiDxe: Setup requests and completions rings
These rings are shared memory buffers between host and device in which
a cyclic buffer is managed to send request descriptors from host to
device and receive completion descriptors from device to
These rings are shared memory buffers between host and device in which
a cyclic buffer is managed to send request descriptors from host to
device and receive completion descriptors from device to
|
By
Liran Alon
·
#56546
·
|
|
[PATCH v3 12/17] OvmfPkg/PvScsiDxe: Reset adapter on init
The following commits will complete the implementation of
device initialization.
Ref: https://bugzilla.tianocore.org/show_bug.cgi?id=2567
Reviewed-by: Laszlo Ersek <lersek@...>
Signed-off-by:
The following commits will complete the implementation of
device initialization.
Ref: https://bugzilla.tianocore.org/show_bug.cgi?id=2567
Reviewed-by: Laszlo Ersek <lersek@...>
Signed-off-by:
|
By
Liran Alon
·
#56545
·
|
|
[PATCH v3 11/17] OvmfPkg/PvScsiDxe: Define device interface structures and constants
These definitions will be used by the following commits to complete the
implementation of PVSCSI device driver.
Ref: https://bugzilla.tianocore.org/show_bug.cgi?id=2567
Acked-by: Laszlo Ersek
These definitions will be used by the following commits to complete the
implementation of PVSCSI device driver.
Ref: https://bugzilla.tianocore.org/show_bug.cgi?id=2567
Acked-by: Laszlo Ersek
|
By
Liran Alon
·
#56544
·
|
|
[PATCH v3 10/17] OvmfPkg/PvScsiDxe: Enable MMIO-Space & Bus-Mastering in PCI attributes
Enable MMIO-Space & Bus-Mastering PCI attributes when device is started.
Note that original PCI attributes are restored when device is stopped.
Ref:
Enable MMIO-Space & Bus-Mastering PCI attributes when device is started.
Note that original PCI attributes are restored when device is stopped.
Ref:
|
By
Liran Alon
·
#56543
·
|
|
[PATCH v3 09/17] OvmfPkg/PvScsiDxe: Backup/Restore PCI attributes on Init/UnInit
This commit doesn't change semantics.
It is done as a preparation for future commits which will modify
PCI attributes.
Ref: https://bugzilla.tianocore.org/show_bug.cgi?id=2567
Reviewed-by: Laszlo
This commit doesn't change semantics.
It is done as a preparation for future commits which will modify
PCI attributes.
Ref: https://bugzilla.tianocore.org/show_bug.cgi?id=2567
Reviewed-by: Laszlo
|
By
Liran Alon
·
#56542
·
|
|
[PATCH v3 08/17] OvmfPkg/PvScsiDxe: Open PciIo protocol for later use
This will give us an exclusive access to the PciIo of this device
after it was started and until it will be stopped.
Ref: https://bugzilla.tianocore.org/show_bug.cgi?id=2567
Reviewed-by: Laszlo Ersek
This will give us an exclusive access to the PciIo of this device
after it was started and until it will be stopped.
Ref: https://bugzilla.tianocore.org/show_bug.cgi?id=2567
Reviewed-by: Laszlo Ersek
|
By
Liran Alon
·
#56541
·
|
|
[PATCH v3 07/17] OvmfPkg/PvScsiDxe: Translate Target & LUN to/from DevicePath
Implement EXT_SCSI_PASS_THRU.BuildDevicePath() and
EXT_SCSI_PASS_THRU.GetTargetLun().
Ref: https://bugzilla.tianocore.org/show_bug.cgi?id=2567
Reviewed-by: Laszlo Ersek
Implement EXT_SCSI_PASS_THRU.BuildDevicePath() and
EXT_SCSI_PASS_THRU.GetTargetLun().
Ref: https://bugzilla.tianocore.org/show_bug.cgi?id=2567
Reviewed-by: Laszlo Ersek
|
By
Liran Alon
·
#56540
·
|
|
[PATCH v3 06/17] OvmfPkg/PvScsiDxe: Report the number of targets and LUNs
Implement EXT_SCSI_PASS_THRU.GetNextTarget() and
EXT_SCSI_PASS_THRU.GetNextTargetLun().
ScsiBusDxe scans all MaxTarget * MaxLun possible devices.
This can take unnecessarily long for large number of
Implement EXT_SCSI_PASS_THRU.GetNextTarget() and
EXT_SCSI_PASS_THRU.GetNextTargetLun().
ScsiBusDxe scans all MaxTarget * MaxLun possible devices.
This can take unnecessarily long for large number of
|
By
Liran Alon
·
#56539
·
|
|
[PATCH v3 05/17] OvmfPkg/PvScsiDxe: Install stubbed EXT_SCSI_PASS_THRU
Support dynamic insertion and removal of the protocol.
Ref: https://bugzilla.tianocore.org/show_bug.cgi?id=2567
Reviewed-by: Laszlo Ersek <lersek@...>
Signed-off-by: Liran Alon
Support dynamic insertion and removal of the protocol.
Ref: https://bugzilla.tianocore.org/show_bug.cgi?id=2567
Reviewed-by: Laszlo Ersek <lersek@...>
Signed-off-by: Liran Alon
|
By
Liran Alon
·
#56538
·
|
|
[PATCH v3 04/17] OvmfPkg/PvScsiDxe: Probe PCI devices and look for PvScsi
PvScsiControllerSupported() is called on handles passed in
by the ConnectController() boot service and if the handle is the
PVSCSI controller, the function would return success. A success
return value
PvScsiControllerSupported() is called on handles passed in
by the ConnectController() boot service and if the handle is the
PVSCSI controller, the function would return success. A success
return value
|
By
Liran Alon
·
#56537
·
|
|
[PATCH v3 03/17] OvmfPkg/PvScsiDxe: Report name of driver
Install Component Name protocols to have a nice display name for the
driver in places such as UEFI shell.
Ref: https://bugzilla.tianocore.org/show_bug.cgi?id=2567
Reviewed-by: Laszlo Ersek
Install Component Name protocols to have a nice display name for the
driver in places such as UEFI shell.
Ref: https://bugzilla.tianocore.org/show_bug.cgi?id=2567
Reviewed-by: Laszlo Ersek
|
By
Liran Alon
·
#56536
·
|
|
[PATCH v3 02/17] OvmfPkg/PvScsiDxe: Install DriverBinding protocol
In order to probe and connect to the PvScsi device we need this
protocol. Currently it does nothing.
Ref: https://bugzilla.tianocore.org/show_bug.cgi?id=2567
Reviewed-by: Laszlo Ersek
In order to probe and connect to the PvScsi device we need this
protocol. Currently it does nothing.
Ref: https://bugzilla.tianocore.org/show_bug.cgi?id=2567
Reviewed-by: Laszlo Ersek
|
By
Liran Alon
·
#56535
·
|