From: Juergen Gross <jgross@suse.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Len Brown <lenb@kernel.org>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org,
x86@kernel.org, linux-acpi@vger.kernel.org
Subject: Re: [PATCH v2 6/7] xen: allow mapping ACPI data using a different physical address
Date: Tue, 10 Sep 2024 10:15:34 +0200 [thread overview]
Message-ID: <b6bb45ab-23bb-458d-a8db-9619f594e8c7@suse.com> (raw)
In-Reply-To: <607602c3-5199-4326-8676-d28a8b42b4b5@suse.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 1833 bytes --]
On 20.08.24 11:56, Jan Beulich wrote:
> On 20.08.2024 10:20, Juergen Gross wrote:
>> @@ -838,6 +839,31 @@ void __init xen_do_remap_nonram(void)
>> pr_info("Remapped %u non-RAM page(s)\n", remapped);
>> }
>>
>> +/*
>> + * Xen variant of acpi_os_ioremap() taking potentially remapped non-RAM
>> + * regions into acount.
>> + * Any attempt to map an area crossing a remap boundary will produce a
>> + * WARN() splat.
>> + */
>> +static void __iomem *xen_acpi_os_ioremap(acpi_physical_address phys,
>> + acpi_size size)
>> +{
>> + unsigned int i;
>> + struct nonram_remap *remap = xen_nonram_remap;
>
> const (also in one of the functions in patch 5)?
Yes.
>
>> + for (i = 0; i < nr_nonram_remap; i++) {
>> + if (phys + size > remap->maddr &&
>> + phys < remap->maddr + remap->size) {
>> + WARN_ON(phys < remap->maddr ||
>> + phys + size > remap->maddr + remap->size);
>> + phys = remap->paddr + phys - remap->maddr;
>> + break;
>> + }
>> + }
>> +
>> + return x86_acpi_os_ioremap(phys, size);
>> +}
>
> At least this, perhaps also what patch 5 adds, likely wants to be limited
> to the XEN_DOM0 case? Or else I wonder whether ...
>
>> @@ -850,6 +876,10 @@ void __init xen_add_remap_nonram(phys_addr_t maddr, phys_addr_t paddr,
>> BUG();
>> }
>>
>> + /* Switch to the Xen acpi_os_ioremap() variant. */
>> + if (nr_nonram_remap == 0)
>> + acpi_os_ioremap = xen_acpi_os_ioremap;
>
> ... this would actually build when XEN_DOM0=n.
>
> I'm actually surprised there's no Dom0-only code section in this file,
> where the new code could then simply be inserted.
I'd rather make this conditional on CONFIG_ACPI.
Depending on how Xen tools will handle a PV-domain with "e820_host=1" this
code might be important for domUs, too.
Juergen
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3743 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
next prev parent reply other threads:[~2024-09-10 8:15 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-20 8:20 [PATCH v2 0/7] xen: fix dom0 PV boot on some AMD machines Juergen Gross
2024-08-20 8:20 ` [PATCH v2 1/7] xen: use correct end address of kernel for conflict checking Juergen Gross
2024-08-20 8:29 ` Jan Beulich
2024-08-20 8:20 ` [PATCH v2 2/7] xen: introduce generic helper checking for memory map conflicts Juergen Gross
2024-08-20 8:35 ` Jan Beulich
2024-08-22 11:29 ` Jürgen Groß
2024-08-20 8:20 ` [PATCH v2 3/7] xen: move checks for e820 conflicts further up Juergen Gross
2024-08-20 8:40 ` Jan Beulich
2024-08-20 8:20 ` [PATCH v2 4/7] xen: move max_pfn in xen_memory_setup() out of function scope Juergen Gross
2024-08-20 8:44 ` Jan Beulich
2024-08-22 11:38 ` Jürgen Groß
2024-08-20 8:20 ` [PATCH v2 5/7] xen: add capability to remap non-RAM pages to different PFNs Juergen Gross
2024-08-20 9:38 ` Jan Beulich
2024-09-10 7:59 ` Jürgen Groß
2024-08-20 8:20 ` [PATCH v2 6/7] xen: allow mapping ACPI data using a different physical address Juergen Gross
2024-08-20 9:56 ` Jan Beulich
2024-09-10 8:15 ` Juergen Gross [this message]
2024-09-10 8:54 ` Jan Beulich
2024-08-20 17:37 ` kernel test robot
2024-08-20 19:39 ` kernel test robot
2024-08-20 8:20 ` [PATCH v2 7/7] xen: tolerate ACPI NVS memory overlapping with Xen allocated memory Juergen Gross
2024-08-20 10:23 ` Jan Beulich
2024-09-10 8:16 ` Jürgen Groß
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=b6bb45ab-23bb-458d-a8db-9619f594e8c7@suse.com \
--to=jgross@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jbeulich@suse.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rafael@kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xenproject.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
all inboxes | Powered by JetHome®