From: igor.druzhinin@citrix.com
To: Anthony PERARD <anthony.perard@citrix.com>
Cc: <devel@edk2.groups.io>, <xen-devel@lists.xenproject.org>,
<jordan.l.justen@intel.com>, <lersek@redhat.com>,
<ard.biesheuvel@arm.com>, <julien@xen.org>
Subject: Re: [PATCH] OvmfPkg/XenPlatformPei: Grab 64-bit PCI MMIO hole size from OVMF info table
Date: Tue, 19 Jan 2021 13:25:25 +0000 [thread overview]
Message-ID: <63cf6053-9787-d8cf-db18-982ebcab1780@citrix.com> (raw)
In-Reply-To: <YAbckZdzHFcnH7ea@perard.uk.xensource.com>
On 19/01/2021 13:20, Anthony PERARD wrote:
> On Mon, Jan 11, 2021 at 03:45:18AM +0000, Igor Druzhinin wrote:
>> diff --git a/OvmfPkg/XenPlatformPei/MemDetect.c b/OvmfPkg/XenPlatformPei/MemDetect.c
>> index 1f81eee..4175a2f 100644
>> --- a/OvmfPkg/XenPlatformPei/MemDetect.c
>> +++ b/OvmfPkg/XenPlatformPei/MemDetect.c
>> @@ -227,6 +227,7 @@ GetFirstNonAddress (
>> UINT64 FirstNonAddress;
>> UINT64 Pci64Base, Pci64Size;
>> RETURN_STATUS PcdStatus;
>> + EFI_STATUS Status;
>>
>> FirstNonAddress = BASE_4GB + GetSystemMemorySizeAbove4gb ();
>>
>> @@ -245,7 +246,10 @@ GetFirstNonAddress (
>> // Otherwise, in order to calculate the highest address plus one, we must
>> // consider the 64-bit PCI host aperture too. Fetch the default size.
>> //
>> - Pci64Size = PcdGet64 (PcdPciMmio64Size);
>> + Status = XenGetPciMmioInfo (NULL, NULL, &Pci64Base, &Pci64Size);
>
> Pci64Base is overridden later (25 line bellow) by the value from
> FirstNonAddress, shouldn't this be avoided?
> Pci64Base = ALIGN_VALUE (FirstNonAddress, (UINT64)SIZE_1GB);
>
>> diff --git a/OvmfPkg/XenPlatformPei/Xen.h b/OvmfPkg/XenPlatformPei/Xen.h
>> index 2605481..c6e5fbb 100644
>> --- a/OvmfPkg/XenPlatformPei/Xen.h
>> +++ b/OvmfPkg/XenPlatformPei/Xen.h
>> @@ -34,6 +34,16 @@ typedef struct {
>> EFI_PHYSICAL_ADDRESS E820;
>> UINT32 E820EntriesCount;
>> } EFI_XEN_OVMF_INFO;
>> +
>> +// This extra table gives layout of PCI apertures in a Xen guest
>> +#define OVMF_INFO_PCI_TABLE 0
>> +
>> +typedef struct {
>> + EFI_PHYSICAL_ADDRESS LowStart;
>> + EFI_PHYSICAL_ADDRESS LowEnd;
>> + EFI_PHYSICAL_ADDRESS HiStart;
>> + EFI_PHYSICAL_ADDRESS HiEnd;
>
> In the hvmloader patch, these are uint64. It doesn't seems like a good
> idea to use the type EFI_PHYSICAL_ADDRESS here. Could you change to
> UINT64 here?
>
> (even if EFI_PHYSICAL_ADDRESS seems to always be UINT64, in the source
> code.)
>
Anthony, this patch is obsolete now - see discussion between Jan and Laszlo.
The new patch is:
https://lists.xenproject.org/archives/html/xen-devel/2021-01/msg00789.html
Igor
prev parent reply other threads:[~2021-01-19 13:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-11 3:45 [PATCH] OvmfPkg/XenPlatformPei: Grab 64-bit PCI MMIO hole size from OVMF info table Igor Druzhinin
2021-01-11 8:10 ` Laszlo Ersek
2021-01-19 13:20 ` Anthony PERARD
2021-01-19 13:25 ` igor.druzhinin [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-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=63cf6053-9787-d8cf-db18-982ebcab1780@citrix.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