All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Christian König" <christian.koenig@amd.com>
To: "Liu01, Tong (Esther)" <Tong.Liu01@amd.com>,
	"Koenig, Christian" <Christian.Koenig@amd.com>,
	"Chang, HaiJun" <HaiJun.Chang@amd.com>,
	"amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>,
	"Zhang, Bokun" <Bokun.Zhang@amd.com>,
	"Deucher, Alexander" <Alexander.Deucher@amd.com>
Cc: "Xiao, Jack" <Jack.Xiao@amd.com>,
	"Wang, Yang\(Kevin\)" <KevinYang.Wang@amd.com>,
	"Xu, Feifei" <Feifei.Xu@amd.com>,
	"Chen, Horace" <Horace.Chen@amd.com>,
	"Tuikov, Luben" <Luben.Tuikov@amd.com>,
	"Sohail, Rashid" <Rashid.Sohail@amd.com>,
	"Quan, Evan" <Evan.Quan@amd.com>, "Liu, Monk" <Monk.Liu@amd.com>,
	"Zhang, Hawking" <Hawking.Zhang@amd.com>
Subject: Re: [PATCH] drm/amdgpu: add vram reservation logic based on vram_usagebyfirmware_v2_2
Date: Thu, 10 Nov 2022 11:49:38 +0100	[thread overview]
Message-ID: <35396c13-7b1d-cd22-e37b-435b49a329df@amd.com> (raw)
In-Reply-To: <DM4PR12MB6134D1E356397E4F644EF0E290019@DM4PR12MB6134.namprd12.prod.outlook.com>

My Acked-by should be sufficient as well.

For a Reviewed-by I would need to have more background on the atombios 
tables. Alex is the expert on that.

Regards,
Christian.

Am 10.11.22 um 11:47 schrieb Liu01, Tong (Esther):
> [AMD Official Use Only - General]
>
> Hi @Deucher, Alexander & @Koenig, Christian,
>
> Can you give me a Reviewed by:? Now the CI job must has Reviewed by then the patch can be passed. Patch is in the attachment. Thanks a lot.
>
> Kind regards,
> Esther
>
> -----Original Message-----
> From: Koenig, Christian <Christian.Koenig@amd.com>
> Sent: 2022年11月10日星期四 下午6:18
> To: Liu01, Tong (Esther) <Tong.Liu01@amd.com>; Chang, HaiJun <HaiJun.Chang@amd.com>; amd-gfx@lists.freedesktop.org; Zhang, Bokun <Bokun.Zhang@amd.com>
> Cc: Quan, Evan <Evan.Quan@amd.com>; Chen, Horace <Horace.Chen@amd.com>; Tuikov, Luben <Luben.Tuikov@amd.com>; Deucher, Alexander <Alexander.Deucher@amd.com>; Xiao, Jack <Jack.Xiao@amd.com>; Zhang, Hawking <Hawking.Zhang@amd.com>; Liu, Monk <Monk.Liu@amd.com>; Xu, Feifei <Feifei.Xu@amd.com>; Wang, Yang(Kevin) <KevinYang.Wang@amd.com>; Sohail, Rashid <Rashid.Sohail@amd.com>
> Subject: Re: [PATCH] drm/amdgpu: add vram reservation logic based on vram_usagebyfirmware_v2_2
>
> Feel free to add my Acked-by: Christian König <christian.koenig@amd.com> to the patch.
>
> Luben might have some additional comments, but in general I think the biggest problem here is the mail settings.
>
> Somehow either the mail client or the mail server are corrupting the patch.
>
> Regards,
> Christian.
>
> Am 10.11.22 um 11:14 schrieb Liu01, Tong (Esther):
>> [AMD Official Use Only - General]
>>
>> Hi Christian,
>>
>> Please find the attached patch, thanks!
>>
>> Kind regards,
>> Esther
>>
>> -----Original Message-----
>> From: Koenig, Christian <Christian.Koenig@amd.com>
>> Sent: 2022年11月8日星期二 下午10:04
>> To: Chang, HaiJun <HaiJun.Chang@amd.com>; Liu01, Tong (Esther)
>> <Tong.Liu01@amd.com>; amd-gfx@lists.freedesktop.org; Zhang, Bokun
>> <Bokun.Zhang@amd.com>
>> Cc: Quan, Evan <Evan.Quan@amd.com>; Chen, Horace
>> <Horace.Chen@amd.com>; Tuikov, Luben <Luben.Tuikov@amd.com>; Deucher,
>> Alexander <Alexander.Deucher@amd.com>; Xiao, Jack <Jack.Xiao@amd.com>;
>> Zhang, Hawking <Hawking.Zhang@amd.com>; Liu, Monk <Monk.Liu@amd.com>;
>> Xu, Feifei <Feifei.Xu@amd.com>; Wang, Yang(Kevin)
>> <KevinYang.Wang@amd.com>; Sohail, Rashid <Rashid.Sohail@amd.com>
>> Subject: Re: [PATCH] drm/amdgpu: add vram reservation logic based on
>> vram_usagebyfirmware_v2_2
>>
>> Yeah, I mean the code looks correct.
>>
>> It's just that style problems are usually pointed out by automated checkers, especially things like dos line endings.
>>
>> So get that fixed and we can push it immediately.
>>
>> Thanks,
>> Christian.
>>
>> Am 08.11.22 um 14:49 schrieb Chang, HaiJun:
>>> [AMD Official Use Only - General]
>>>
>>> + Bokun to help addressing the coding style problem in MKM side.
>>>
>>> -----Original Message-----
>>> From: Koenig, Christian <Christian.Koenig@amd.com>
>>> Sent: Tuesday, November 8, 2022 8:53 PM
>>> To: Liu01, Tong (Esther) <Tong.Liu01@amd.com>;
>>> amd-gfx@lists.freedesktop.org
>>> Cc: Quan, Evan <Evan.Quan@amd.com>; Chen, Horace
>>> <Horace.Chen@amd.com>; Tuikov, Luben <Luben.Tuikov@amd.com>; Deucher,
>>> Alexander <Alexander.Deucher@amd.com>; Xiao, Jack
>>> <Jack.Xiao@amd.com>; Zhang, Hawking <Hawking.Zhang@amd.com>; Liu,
>>> Monk <Monk.Liu@amd.com>; Xu, Feifei <Feifei.Xu@amd.com>; Wang,
>>> Yang(Kevin) <KevinYang.Wang@amd.com>; Chang, HaiJun
>>> <HaiJun.Chang@amd.com>; Sohail, Rashid <Rashid.Sohail@amd.com>
>>> Subject: Re: [PATCH] drm/amdgpu: add vram reservation logic based on
>>> vram_usagebyfirmware_v2_2
>>>
>>> Hi Esther
>>>
>>> well there are a couple of things which you need to address before getting this merged.
>>>
>>> First of all the patch you send out uses dos line endings instead of the unix line endings. Not sure how you manage to do that, but please use "git send-email" instead to avoid that.
>>>
>>> Then your patch contains a bunch of white spaces after code warning which checkpatch.pl complains about (after ignoring the dos line ending warnings). So this was clearly not properly checked with checkpatch.pl.
>>>
>>> Then the kernel coding style usually says that with a multi line "if ("
>>> the next lines should start after the opening "(". In other words intend with tabs and the whitespaces. I'm not sure what editor you are using, but there are standard settings available for basically all large editors which does stuff like that automatically. Please try to use one of those.
>>>
>>> Regarding the casing of the values it's a good argument that you only move the code around, but the general coding style is just extremely questionable. The defines should use the lowest necessary integer type.
>>> But it's correct that this should probably be part of another patch.
>>>
>>> Regards,
>>> Christian.
>>>
>>> Am 08.11.22 um 11:40 schrieb Liu01, Tong (Esther):
>>>> [AMD Official Use Only - General]
>>>>
>>>> Hi @Koenig, Christian,
>>>>
>>>> Refined as your comment. By the way:
>>>> if ((start_addr & ATOM_VRAM_OPERATION_FLAGS_MASK) ==
>>>> +             (uint32_t)(ATOM_VRAM_BLOCK_SRIOV_MSG_SHARE_RESERVATION <<
>>>> +             ATOM_VRAM_OPERATION_FLAGS_SHIFT))
>>>>
>>>> This part is the old code, I just move it out from the original function to shrink the function size as your comment before. And now I just removed the first uint32_t since if remove both will cause "warning: bitwise comparison always evaluates to false". And I tested the code after removing the first uint32_t, the code works well. Please review the new patch, thanks.
>>>>
>>>> Kind regards,
>>>> Esther
>>>>
>>>> -----Original Message-----
>>>> From: Tong Liu01 <Tong.Liu01@amd.com>
>>>> Sent: 2022年11月8日星期二 下午6:33
>>>> To: amd-gfx@lists.freedesktop.org
>>>> Cc: Quan, Evan <Evan.Quan@amd.com>; Chen, Horace
>>>> <Horace.Chen@amd.com>; Tuikov, Luben <Luben.Tuikov@amd.com>; Koenig,
>>>> Christian <Christian.Koenig@amd.com>; Deucher, Alexander
>>>> <Alexander.Deucher@amd.com>; Xiao, Jack <Jack.Xiao@amd.com>; Zhang,
>>>> Hawking <Hawking.Zhang@amd.com>; Liu, Monk <Monk.Liu@amd.com>; Xu,
>>>> Feifei <Feifei.Xu@amd.com>; Wang, Yang(Kevin)
>>>> <KevinYang.Wang@amd.com>; Liu01, Tong (Esther) <Tong.Liu01@amd.com>
>>>> Subject: [PATCH] drm/amdgpu: add vram reservation logic based on
>>>> vram_usagebyfirmware_v2_2
>>>>
>>>> Move TMR region from top of FB to 2MB for FFBM, so we need to
>>>> reserve TMR region firstly to make sure TMR can be allocated at 2MB
>>>>
>>>> Signed-off-by: Tong Liu01 <Tong.Liu01@amd.com>
>>>> ---
>>>>      .../gpu/drm/amd/amdgpu/amdgpu_atomfirmware.c  | 106 ++++++++++++++----
>>>>      drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c       |  50 +++++++++
>>>>      drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.h       |   5 +
>>>>      drivers/gpu/drm/amd/include/atomfirmware.h    |  62 ++++++++--
>>>>      4 files changed, 192 insertions(+), 31 deletions(-)
>>>>
>>>> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_atomfirmware.c
>>>> b/drivers/gpu/drm/amd/amdgpu/amdgpu_atomfirmware.c
>>>> index b81b77a9efa6..032dc2678d7c 100644
>>>> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_atomfirmware.c
>>>> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_atomfirmware.c
>>>> @@ -101,39 +101,99 @@ void amdgpu_atomfirmware_scratch_regs_init(struct amdgpu_device *adev)
>>>>          }
>>>>      }
>>>>
>>>> +static int amdgpu_atomfirmware_allocate_fb_v2_1(struct amdgpu_device *adev,
>>>> +             struct vram_usagebyfirmware_v2_1 *firmware_usage_v2_1,
>>>> +             int *usage_bytes)
>>>> +{
>>>> +     uint32_t start_addr, fw_size, drv_size;
>>>> +
>>>> +     start_addr = le32_to_cpu(firmware_usage_v2_1->start_address_in_kb);
>>>> +     fw_size = le16_to_cpu(firmware_usage_v2_1->used_by_firmware_in_kb);
>>>> +     drv_size =
>>>> + le16_to_cpu(firmware_usage_v2_1->used_by_driver_in_kb);
>>>> +
>>>> +     DRM_DEBUG("atom firmware v2_1 requested %08x %dkb fw %dkb drv\n",
>>>> +             start_addr,
>>>> +             fw_size,
>>>> +             drv_size);
>>>> +
>>>> +     if ((start_addr & ATOM_VRAM_OPERATION_FLAGS_MASK) ==
>>>> +             (uint32_t)(ATOM_VRAM_BLOCK_SRIOV_MSG_SHARE_RESERVATION <<
>>>> +             ATOM_VRAM_OPERATION_FLAGS_SHIFT)) {
>>>> +             /* Firmware request VRAM reservation for SR-IOV */
>>>> +             adev->mman.fw_vram_usage_start_offset = (start_addr &
>>>> +                     (~ATOM_VRAM_OPERATION_FLAGS_MASK)) << 10;
>>>> +             adev->mman.fw_vram_usage_size = fw_size << 10;
>>>> +             /* Use the default scratch size */
>>>> +             *usage_bytes = 0;
>>>> +     } else {
>>>> +             *usage_bytes = drv_size << 10;
>>>> +     }
>>>> +     return 0;
>>>> +}
>>>> +
>>>> +static int amdgpu_atomfirmware_allocate_fb_v2_2(struct amdgpu_device *adev,
>>>> +             struct vram_usagebyfirmware_v2_2 *firmware_usage_v2_2,
>>>> +             int *usage_bytes)
>>>> +{
>>>> +     uint32_t fw_start_addr, fw_size, drv_start_addr, drv_size;
>>>> +
>>>> +     fw_start_addr = le32_to_cpu(firmware_usage_v2_2->fw_region_start_address_in_kb);
>>>> +     fw_size =
>>>> + le16_to_cpu(firmware_usage_v2_2->used_by_firmware_in_kb);
>>>> +
>>>> +     drv_start_addr = le32_to_cpu(firmware_usage_v2_2->driver_region0_start_address_in_kb);
>>>> +     drv_size =
>>>> +le32_to_cpu(firmware_usage_v2_2->used_by_driver_region0_in_kb);
>>>> +
>>>> +     DRM_DEBUG("atom requested fw start at %08x %dkb and drv start at %08x %dkb\n",
>>>> +             fw_start_addr,
>>>> +             fw_size,
>>>> +             drv_start_addr,
>>>> +             drv_size);
>>>> +
>>>> +     if ((fw_start_addr & (ATOM_VRAM_BLOCK_NEEDS_NO_RESERVATION << 30)) == 0) {
>>>> +             /* Firmware request VRAM reservation for SR-IOV */
>>>> +             adev->mman.fw_vram_usage_start_offset = (fw_start_addr &
>>>> +                     (~ATOM_VRAM_OPERATION_FLAGS_MASK)) << 10;
>>>> +             adev->mman.fw_vram_usage_size = fw_size << 10;
>>>> +     }
>>>> +
>>>> +     if ((drv_start_addr & (ATOM_VRAM_BLOCK_NEEDS_NO_RESERVATION << 30)) == 0) {
>>>> +             /* driver request VRAM reservation for SR-IOV */
>>>> +             adev->mman.drv_vram_usage_start_offset = (drv_start_addr &
>>>> +                     (~ATOM_VRAM_OPERATION_FLAGS_MASK)) << 10;
>>>> +             adev->mman.drv_vram_usage_size = drv_size << 10;
>>>> +     }
>>>> +
>>>> +     *usage_bytes = 0;
>>>> +     return 0;
>>>> +}
>>>> +
>>>>      int amdgpu_atomfirmware_allocate_fb_scratch(struct amdgpu_device *adev)  {
>>>>          struct atom_context *ctx = adev->mode_info.atom_context;
>>>>          int index = get_index_into_master_table(atom_master_list_of_data_tables_v2_1,
>>>>                                                  vram_usagebyfirmware);
>>>> -     struct vram_usagebyfirmware_v2_1 *firmware_usage;
>>>> -     uint32_t start_addr, size;
>>>> +     struct vram_usagebyfirmware_v2_1 *firmware_usage_v2_1;
>>>> +     struct vram_usagebyfirmware_v2_2 *firmware_usage_v2_2;
>>>>          uint16_t data_offset;
>>>> +     uint8_t frev, crev;
>>>>          int usage_bytes = 0;
>>>>
>>>> -     if (amdgpu_atom_parse_data_header(ctx, index, NULL, NULL, NULL, &data_offset)) {
>>>> -             firmware_usage = (struct vram_usagebyfirmware_v2_1 *)(ctx->bios + data_offset);
>>>> -             DRM_DEBUG("atom firmware requested %08x %dkb fw %dkb drv\n",
>>>> -                       le32_to_cpu(firmware_usage->start_address_in_kb),
>>>> -                       le16_to_cpu(firmware_usage->used_by_firmware_in_kb),
>>>> -                       le16_to_cpu(firmware_usage->used_by_driver_in_kb));
>>>> -
>>>> -             start_addr = le32_to_cpu(firmware_usage->start_address_in_kb);
>>>> -             size = le16_to_cpu(firmware_usage->used_by_firmware_in_kb);
>>>> -
>>>> -             if ((uint32_t)(start_addr & ATOM_VRAM_OPERATION_FLAGS_MASK) ==
>>>> -                     (uint32_t)(ATOM_VRAM_BLOCK_SRIOV_MSG_SHARE_RESERVATION <<
>>>> -                     ATOM_VRAM_OPERATION_FLAGS_SHIFT)) {
>>>> -                     /* Firmware request VRAM reservation for SR-IOV */
>>>> -                     adev->mman.fw_vram_usage_start_offset = (start_addr &
>>>> -                             (~ATOM_VRAM_OPERATION_FLAGS_MASK)) << 10;
>>>> -                     adev->mman.fw_vram_usage_size = size << 10;
>>>> -                     /* Use the default scratch size */
>>>> -                     usage_bytes = 0;
>>>> -             } else {
>>>> -                     usage_bytes = le16_to_cpu(firmware_usage->used_by_driver_in_kb) << 10;
>>>> +     if (amdgpu_atom_parse_data_header(ctx, index, NULL, &frev, &crev, &data_offset)) {
>>>> +             if (frev == 2 && crev == 1) {
>>>> +                     firmware_usage_v2_1 =
>>>> +                             (struct vram_usagebyfirmware_v2_1 *)(ctx->bios + data_offset);
>>>> +                     amdgpu_atomfirmware_allocate_fb_v2_1(adev,
>>>> +                                     firmware_usage_v2_1,
>>>> +                                     &usage_bytes);
>>>> +             } else if (frev >= 2 && crev >= 2) {
>>>> +                     firmware_usage_v2_2 =
>>>> +                             (struct vram_usagebyfirmware_v2_2 *)(ctx->bios + data_offset);
>>>> +                     amdgpu_atomfirmware_allocate_fb_v2_2(adev,
>>>> +                                     firmware_usage_v2_2,
>>>> +                                     &usage_bytes);
>>>>                  }
>>>>          }
>>>> +
>>>>          ctx->scratch_size_bytes = 0;
>>>>          if (usage_bytes == 0)
>>>>                  usage_bytes = 20 * 1024; diff --git
>>>> a/drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c
>>>> b/drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c
>>>> index 585460ab8dfd..4a73cb314086 100644
>>>> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c
>>>> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c
>>>> @@ -1578,6 +1578,22 @@ static void amdgpu_ttm_fw_reserve_vram_fini(struct amdgpu_device *adev)
>>>>                  NULL, &adev->mman.fw_vram_usage_va);
>>>>      }
>>>>
>>>> +/*
>>>> + * Driver Reservation functions
>>>> + */
>>>> +/**
>>>> + * amdgpu_ttm_drv_reserve_vram_fini - free drv reserved vram
>>>> + *
>>>> + * @adev: amdgpu_device pointer
>>>> + *
>>>> + * free drv reserved vram if it has been reserved.
>>>> + */
>>>> +static void amdgpu_ttm_drv_reserve_vram_fini(struct amdgpu_device
>>>> +*adev) {
>>>> +     amdgpu_bo_free_kernel(&adev->mman.drv_vram_usage_reserved_bo,
>>>> +             NULL, NULL);
>>>> +}
>>>> +
>>>>      /**
>>>>       * amdgpu_ttm_fw_reserve_vram_init - create bo vram reservation from fw
>>>>       *
>>>> @@ -1604,6 +1620,31 @@ static int amdgpu_ttm_fw_reserve_vram_init(struct amdgpu_device *adev)
>>>>                                            &adev->mman.fw_vram_usage_va);
>>>>      }
>>>>
>>>> +/**
>>>> + * amdgpu_ttm_drv_reserve_vram_init - create bo vram reservation
>>>> +from driver
>>>> + *
>>>> + * @adev: amdgpu_device pointer
>>>> + *
>>>> + * create bo vram reservation from drv.
>>>> + */
>>>> +static int amdgpu_ttm_drv_reserve_vram_init(struct amdgpu_device
>>>> +*adev) {
>>>> +     uint64_t vram_size = adev->gmc.visible_vram_size;
>>>> +
>>>> +     adev->mman.drv_vram_usage_reserved_bo = NULL;
>>>> +
>>>> +     if (adev->mman.drv_vram_usage_size == 0 ||
>>>> +         adev->mman.drv_vram_usage_size > vram_size)
>>>> +             return 0;
>>>> +
>>>> +     return amdgpu_bo_create_kernel_at(adev,
>>>> +                                       adev->mman.drv_vram_usage_start_offset,
>>>> +                                       adev->mman.drv_vram_usage_size,
>>>> +                                       AMDGPU_GEM_DOMAIN_VRAM,
>>>> +                                       &adev->mman.drv_vram_usage_reserved_bo,
>>>> +                                       NULL); }
>>>> +
>>>>      /*
>>>>       * Memoy training reservation functions
>>>>       */
>>>> @@ -1771,6 +1812,14 @@ int amdgpu_ttm_init(struct amdgpu_device *adev)
>>>>                  return r;
>>>>          }
>>>>
>>>> +     /*
>>>> +      *The reserved vram for driver must be pinned to the specified
>>>> +      *place on the VRAM, so reserve it early.
>>>> +      */
>>>> +     r = amdgpu_ttm_drv_reserve_vram_init(adev);
>>>> +     if (r)
>>>> +             return r;
>>>> +
>>>>          /*
>>>>           * only NAVI10 and onwards ASIC support for IP discovery.
>>>>           * If IP discovery enabled, a block of memory should be @@ -1896,6 +1945,7 @@ void amdgpu_ttm_fini(struct amdgpu_device *adev)
>>>>          amdgpu_bo_free_kernel(&adev->mman.sdma_access_bo, NULL,
>>>>                                          &adev->mman.sdma_access_ptr);
>>>>          amdgpu_ttm_fw_reserve_vram_fini(adev);
>>>> +     amdgpu_ttm_drv_reserve_vram_fini(adev);
>>>>
>>>>          if (drm_dev_enter(adev_to_drm(adev), &idx)) {
>>>>
>>>> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.h
>>>> b/drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.h
>>>> index 9120ae80ef52..339838675b11 100644
>>>> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.h
>>>> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.h
>>>> @@ -92,6 +92,11 @@ struct amdgpu_mman {
>>>>          struct amdgpu_bo        *fw_vram_usage_reserved_bo;
>>>>          void            *fw_vram_usage_va;
>>>>
>>>> +     /* driver VRAM reservation */
>>>> +     u64             drv_vram_usage_start_offset;
>>>> +     u64             drv_vram_usage_size;
>>>> +     struct amdgpu_bo        *drv_vram_usage_reserved_bo;
>>>> +
>>>>          /* PAGE_SIZE'd BO for process memory r/w over SDMA. */
>>>>          struct amdgpu_bo        *sdma_access_bo;
>>>>          void                    *sdma_access_ptr;
>>>> diff --git a/drivers/gpu/drm/amd/include/atomfirmware.h
>>>> b/drivers/gpu/drm/amd/include/atomfirmware.h
>>>> index ff855cb21d3f..c0f56ae653f0 100644
>>>> --- a/drivers/gpu/drm/amd/include/atomfirmware.h
>>>> +++ b/drivers/gpu/drm/amd/include/atomfirmware.h
>>>> @@ -705,20 +705,66 @@ struct atom_gpio_pin_lut_v2_1  };
>>>>
>>>>
>>>> -/*
>>>> -  ***************************************************************************
>>>> -    Data Table vram_usagebyfirmware  structure
>>>> -
>>>> ********************************************************************
>>>> *
>>>> *
>>>> *****
>>>> +/*
>>>> +  VBIOS/PRE-OS always reserve a FB region at the top of frame buffer. driver should not write access that region.
>>>> +  driver can allocate their own reservation region as long as it does not overlap firwmare's reservation region.
>>>> +  if( atom data table firmwareInfoTable version < 3.3) { //( pre-NV1X )
>>>> +    in this case, atom data table vram_usagebyfirmwareTable version always <= 2.1
>>>> +    if( VBIOS/UEFI GOP is posted ) {
>>>> +      VBIOS/UEFIGOP update used_by_firmware_in_kb = total reserved size by VBIOS
>>>> +      update start_address_in_kb = total_mem_size_in_kb - used_by_firmware_in_kb;  ( total_mem_size_in_kb = reg(CONFIG_MEMSIZE)<<10)
>>>> +      driver can allocate driver reservation region under firmware reservation,
>>>> +      used_by_driver_in_kb = driver reservation size
>>>> +      driver reservation start address =  (start_address_in_kb - used_by_driver_in_kb)
>>>> +    Comment1[hchan]: There is only one reservation at the beginning of the FB reserved by Host driver.
>>>> +    Host driver would overwrite the table with the following
>>>> +    used_by_firmware_in_kb = total reserved size for pf-vf info exchange and
>>>> +    set SRIOV_MSG_SHARE_RESERVATION mask start_address_in_kb = 0
>>>> +    } else {
>>>> +      there is no VBIOS reservation region
>>>> +      driver must allocate driver reservation region at top of FB.
>>>> +      driver set used_by_driver_in_kb = driver reservation size
>>>> +      driver reservation start address =  (total_mem_size_in_kb - used_by_driver_in_kb)
>>>> +      same as Comment1
>>>> +    }
>>>> +  } else { //( NV1X and after)
>>>> +    if( VBIOS/UEFI GOP is posted ) {
>>>> +      VBIOS/UEFIGOP update used_by_firmware_in_kb = atom_firmware_Info_v3_3.fw_reserved_size_in_kb;
>>>> +      update start_address_in_kb = total_mem_size_in_kb - used_by_firmware_in_kb;  ( total_mem_size_in_kb = reg(CONFIG_MEMSIZE)<<10  )
>>>> +    }
>>>> +    if( vram_usagebyfirmwareTable version <= 2.1 ) {
>>>> +      driver can allocate driver reservation region under firmware reservation,
>>>> +      driver set used_by_driver_in_kb = driver reservation size
>>>> +      driver reservation start address =  (start_address_in_kb - used_by_driver_in_kb)
>>>> +      same as Comment1
>>>> +    } else {
>>>> +      dirver can allocate it reservation any place as long as it does overlap pre-OS FW reservation area
>>>> +      driver set used_by_driver_region0_in_kb = driver reservation size
>>>> +      driver set driver_region0_start_address_in_kb =  driver reservation region start address
>>>> +      Comment2[hchan]: Host driver can set used_by_firmware_in_kb and start_address_in_kb to zero
>>>> +      as the reservation for VF as it doesn’t exist.  And Host driver should also
>>>> +      update atom_firmware_Info table to remove the same VBIOS reservation as well.
>>>> +    }
>>>> +  }
>>>>      */
>>>>
>>>>      struct vram_usagebyfirmware_v2_1
>>>>      {
>>>> -  struct  atom_common_table_header  table_header;
>>>> -  uint32_t  start_address_in_kb;
>>>> -  uint16_t  used_by_firmware_in_kb;
>>>> -  uint16_t  used_by_driver_in_kb;
>>>> +     struct  atom_common_table_header  table_header;
>>>> +     uint32_t  start_address_in_kb;
>>>> +     uint16_t  used_by_firmware_in_kb;
>>>> +     uint16_t  used_by_driver_in_kb;
>>>>      };
>>>>
>>>> +struct vram_usagebyfirmware_v2_2 {
>>>> +     struct  atom_common_table_header  table_header;
>>>> +     uint32_t  fw_region_start_address_in_kb;
>>>> +     uint16_t  used_by_firmware_in_kb;
>>>> +     uint16_t  reserved;
>>>> +     uint32_t  driver_region0_start_address_in_kb;
>>>> +     uint32_t  used_by_driver_region0_in_kb;
>>>> +     uint32_t  reserved32[7];
>>>> +};
>>>>
>>>>      /*
>>>>
>>>> ********************************************************************
>>>> *
>>>> *
>>>> *****
>>>> --
>>>> 2.25.1


  reply	other threads:[~2022-11-10 10:49 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-08 10:32 [PATCH] drm/amdgpu: add vram reservation logic based on vram_usagebyfirmware_v2_2 Tong Liu01
2022-11-08 10:40 ` Liu01, Tong (Esther)
2022-11-08 12:53   ` Christian König
2022-11-08 13:49     ` Chang, HaiJun
2022-11-08 14:04       ` Christian König
2022-11-08 16:33         ` Luben Tuikov
2022-11-10  5:25           ` Liu01, Tong (Esther)
2022-11-10  9:49             ` Christian König
2022-11-10 15:10             ` Luben Tuikov
2022-11-10 10:14         ` Liu01, Tong (Esther)
2022-11-10 10:18           ` Christian König
2022-11-10 10:47             ` Liu01, Tong (Esther)
2022-11-10 10:49               ` Christian König [this message]
2022-11-10 12:17               ` Lazar, Lijo
  -- strict thread matches above, loose matches on Subject: below --
2022-11-08 17:28 Bokun Zhang
2022-11-08  2:46 Tong Liu01
2022-11-08  7:25 ` Liu01, Tong (Esther)
2022-11-08  9:40 ` Christian König
2022-11-07  3:32 Tong Liu01
2022-11-07 10:33 ` Liu01, Tong (Esther)
2022-11-07 17:47 ` Christian König
2022-11-04 11:01 Tong Liu01
2022-11-07  2:36 ` Liu01, Tong (Esther)
2022-11-04  8:52 Tong Liu01
2022-11-04  9:09 ` Christian König
2022-11-04  9:34   ` Liu01, Tong (Esther)
2022-11-04  9:39     ` Christian König

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=35396c13-7b1d-cd22-e37b-435b49a329df@amd.com \
    --to=christian.koenig@amd.com \
    --cc=Alexander.Deucher@amd.com \
    --cc=Bokun.Zhang@amd.com \
    --cc=Evan.Quan@amd.com \
    --cc=Feifei.Xu@amd.com \
    --cc=HaiJun.Chang@amd.com \
    --cc=Hawking.Zhang@amd.com \
    --cc=Horace.Chen@amd.com \
    --cc=Jack.Xiao@amd.com \
    --cc=KevinYang.Wang@amd.com \
    --cc=Luben.Tuikov@amd.com \
    --cc=Monk.Liu@amd.com \
    --cc=Rashid.Sohail@amd.com \
    --cc=Tong.Liu01@amd.com \
    --cc=amd-gfx@lists.freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.