From: "Kuppuswamy, Sathyanarayanan" <sathyanarayanan.kuppuswamy@linux.intel.com>
To: Thomas Gleixner <tglx@linutronix.de>,
Rafael J Wysocki <rjw@rjwysocki.net>,
Ingo Molnar <mingo@redhat.com>, "H . Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <peterz@infradead.org>
Cc: Len Brown <lenb@kernel.org>,
Robert Moore <robert.moore@intel.com>,
Erik Kaneda <erik.kaneda@intel.com>,
linux-acpi@vger.kernel.org, devel@acpica.org,
linux-kernel@vger.kernel.org, x86@kernel.org,
Sean Christopherson <sean.j.christopherson@intel.com>,
Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH 3/3] x86/acpi, x86/boot: Add multiprocessor wake-up support
Date: Thu, 22 Apr 2021 16:39:46 -0700 [thread overview]
Message-ID: <03d54f69-c172-e2b8-72ec-b91e8e96d643@linux.intel.com> (raw)
In-Reply-To: <87lf99x6nn.ffs@nanos.tec.linutronix.de>
On 4/22/21 4:04 PM, Thomas Gleixner wrote:
> Kuppuswamy!
>
> On Thu, Apr 22 2021 at 12:24, Kuppuswamy Sathyanarayanan wrote:
>> +static int acpi_wakeup_cpu(int apicid, unsigned long start_ip)
>> +{
>> + acpi_mp_wake_mailbox_init();
>> +
>> + if (!acpi_mp_wake_mailbox)
>> + return -EINVAL;
>> +
>> + WRITE_ONCE(acpi_mp_wake_mailbox->apic_id, apicid);
>> + WRITE_ONCE(acpi_mp_wake_mailbox->wakeup_vector, start_ip);
>> + WRITE_ONCE(acpi_mp_wake_mailbox->command, ACPI_MP_WAKE_COMMAND_WAKEUP);
>
> What's the point of using WRITE_ONCE() here? Where is the required
> READ_ONCE() counterpart and the required documentation in form of a
> comment?
mailbox memory is shared between firmware and OS. We use WRITE_ONCE to notify
compiler about it, and also to preserve the order of writes to these
addresses. As per MADT Wake protocol, once OS update the mailbox command
address with ACPI_MP_*_WAKEUP command, firmware will be bring the AP out sleep
state and trigger the boot process.
Since its a one way communication, we don't need to read the mailbox address
again. So there is no corresponding READ_ONCE() call.
I will add some comments about it in next version.
>
>> +static int __init acpi_parse_mp_wake(union acpi_subtable_headers *header,
>> + const unsigned long end)
>> +{
> ...
>> + acpi_wake_cpu_handler_update(acpi_wakeup_cpu);
> ...
>
>> +++ b/arch/x86/kernel/apic/probe_32.c
>> @@ -207,3 +207,11 @@ int __init default_acpi_madt_oem_check(char *oem_id, char *oem_table_id)
>> }
>> return 0;
>> }
>> +
>> +void __init acpi_wake_cpu_handler_update(wakeup_cpu_handler handler)
>> +{
>> + struct apic **drv;
>> +
>> + for (drv = __apicdrivers; drv < __apicdrivers_end; drv++)
>> + (*drv)->wakeup_secondary_cpu = handler;
>> +}
>> diff --git a/arch/x86/kernel/apic/probe_64.c b/arch/x86/kernel/apic/probe_64.c
>> index c46720f185c0..986dbb68d3c4 100644
>> --- a/arch/x86/kernel/apic/probe_64.c
>> +++ b/arch/x86/kernel/apic/probe_64.c
>> @@ -50,3 +50,11 @@ int __init default_acpi_madt_oem_check(char *oem_id, char *oem_table_id)
>> }
>> return 0;
>> }
>> +
>> +void __init acpi_wake_cpu_handler_update(wakeup_cpu_handler handler)
>> +{
>> + struct apic **drv;
>> +
>> + for (drv = __apicdrivers; drv < __apicdrivers_end; drv++)
>> + (*drv)->wakeup_secondary_cpu = handler;
>> +}
>
> What's the reason for having two verbatim copies of the same function
> which has no dependency on CONFIG_*_32/64 at all?
Initially I thought all ACPI related functions are grouped in probe_*.c.
After some review, now I know its incorrect. I will move the function
definition to apic.c
>
> Thanks,
>
> tglx
>
--
Sathyanarayanan Kuppuswamy
Linux Kernel Developer
prev parent reply other threads:[~2021-04-22 23:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-22 19:24 [PATCH 0/3] Add multiprocessor wake-up support Kuppuswamy Sathyanarayanan
2021-04-22 19:24 ` [PATCH 1/3] ACPICA: ACPI 6.4: MADT: add Multiprocessor Wakeup Mailbox Structure Kuppuswamy Sathyanarayanan
2021-04-22 19:37 ` Dave Hansen
2021-04-22 19:46 ` Kuppuswamy, Sathyanarayanan
2021-04-22 19:55 ` Borislav Petkov
2021-04-22 20:51 ` Kaneda, Erik
2021-04-22 21:40 ` Kuppuswamy, Sathyanarayanan
2021-04-22 19:24 ` [PATCH 2/3] ACPI/table: Print MADT Wake table information Kuppuswamy Sathyanarayanan
2021-04-22 19:24 ` [PATCH 3/3] x86/acpi, x86/boot: Add multiprocessor wake-up support Kuppuswamy Sathyanarayanan
2021-04-22 23:04 ` Thomas Gleixner
2021-04-22 23:39 ` Kuppuswamy, Sathyanarayanan [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-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=03d54f69-c172-e2b8-72ec-b91e8e96d643@linux.intel.com \
--to=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=ak@linux.intel.com \
--cc=devel@acpica.org \
--cc=erik.kaneda@intel.com \
--cc=hpa@zytor.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rjw@rjwysocki.net \
--cc=robert.moore@intel.com \
--cc=sean.j.christopherson@intel.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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;
as well as URLs for NNTP newsgroup(s).