From: Yunhong Jiang <yunhong.jiang@linux.intel.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
dave.hansen@linux.intel.com, x86@kernel.org, hpa@zytor.com,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
kys@microsoft.com, haiyangz@microsoft.com, wei.liu@kernel.org,
decui@microsoft.com, rafael@kernel.org, lenb@kernel.org,
kirill.shutemov@linux.intel.com, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, linux-hyperv@vger.kernel.org,
linux-acpi@vger.kernel.org
Subject: Re: [PATCH v2 2/9] dt-bindings: x86: Add a binding for x86 wakeup mailbox
Date: Mon, 9 Sep 2024 23:13:21 -0700 [thread overview]
Message-ID: <20240910061227.GA76@yjiang5-mobl.amr.corp.intel.com> (raw)
In-Reply-To: <20240827204549.GA4545@yjiang5-mobl.amr.corp.intel.com>
On Tue, Aug 27, 2024 at 01:45:49PM -0700, Yunhong Jiang wrote:
> On Sun, Aug 25, 2024 at 09:10:01AM +0200, Krzysztof Kozlowski wrote:
> > On Fri, Aug 23, 2024 at 04:23:20PM -0700, Yunhong Jiang wrote:
> > > Add the binding to use mailbox wakeup mechanism to bringup APs.
> > >
> > > Signed-off-by: Yunhong Jiang <yunhong.jiang@linux.intel.com>
> > > ---
> > > .../devicetree/bindings/x86/wakeup.yaml | 64 +++++++++++++++++++
> > > 1 file changed, 64 insertions(+)
> > > create mode 100644 Documentation/devicetree/bindings/x86/wakeup.yaml
> > >
> > > diff --git a/Documentation/devicetree/bindings/x86/wakeup.yaml b/Documentation/devicetree/bindings/x86/wakeup.yaml
> > > new file mode 100644
> > > index 000000000000..cb84e2756bca
> > > --- /dev/null
> > > +++ b/Documentation/devicetree/bindings/x86/wakeup.yaml
> > > @@ -0,0 +1,64 @@
> > > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> > > +# Copyright (C) 2024 Intel Corporation
> > > +%YAML 1.2
> > > +---
> > > +$id: http://devicetree.org/schemas/x86/wakeup.yaml#
> > > +$schema: http://devicetree.org/meta-schemas/core.yaml#
> > > +
> > > +title: x86 mailbox wakeup
> > > +maintainers:
> > > + - Yunhong Jiang <yunhong.jiang@linux.intel.com>
> > > +
> > > +description: |
> > > + The x86 mailbox wakeup mechanism defines a mechanism to let the bootstrap
> > > + processor (BSP) to wake up application processors (APs) through a wakeup
> > > + mailbox.
> > > +
> > > + The "wakeup-mailbox-addr" property specifies the wakeup mailbox address. The
> > > + wakeup mailbox is a 4K-aligned 4K-size memory block allocated in the reserved
> > > + memory.
> > > +
> > > + The wakeup mailbox structure is defined as follows.
> > > +
> > > + uint16_t command;
> > > + uint16_t reserved;
> > > + uint32_t apic_id;
> > > + uint64_t wakeup_vector;
> > > + uint8_t reservedForOs[2032];
> > > +
> > > + The memory after reservedForOs field is reserved and OS should not touch it.
> > > +
> > > + To wakes up a AP, the BSP prepares the wakeup routine, fills the wakeup
> > > + routine's address into the wakeup_vector field, fill the apic_id field with
> > > + the target AP's APIC_ID, and write 1 to the command field. After receiving the
> > > + wakeup command, the target AP will jump to the wakeup routine.
> > > +
> > > + For each AP, the mailbox can be used only once for the wakeup command. After
> > > + the AP jumps to the wakeup routine, the mailbox will no longer be checked by
> > > + this AP.
> > > +
> > > + The wakeup mailbox structure and the wakeup process is the same as
> > > + the Multiprocessor Wakeup Mailbox Structure defined in ACPI spec version 6.5,
> > > + section 5.2.12.19 [1].
> > > +
> > > + References:
> > > +
> > > + [1] https://uefi.org/specs/ACPI/6.5/05_ACPI_Software_Programming_Model.html
> > > +
> > > +select: false
> >
> > This schema is still a no-op because of this false.
> >
> > What is the point of defining one property if it is not placed anywhere?
> > Every device node can have it? Seems wrong...
> >
> > You need to come with proper schema. Lack of an example is another thing
> > - this cannot be even validated by the tools.
> >
> > Best regards,
> > Krzysztof
Hi, Krzysztof, I'm working to address your comments and have some questions.
Hope to get help/guide from your side.
For the select, the writing-schema.rst describes it as "A json-schema used to
match nodes for applying the schema" but I'm a bit confused. In my case, should
it be "cpus" node? Is there any code/tools that uses this property, so that I
can have a better understanding?
For your "validated by the tools", can you please share the tools you used to
validate the schema? I used "make dt_binding_check" per the
submitting-patches.rst but I think your comments is about another tool.
Sorry for the bothering. I read the DT spec and the
Documentation/devicetree/bindings documents and still not sure.
Than you
--jyh
>
> Thank you for the feedback. Will update the schema file on next round
> submission.
>
> Thanks
> --jyh
>
> >
>
next prev parent reply other threads:[~2024-09-10 6:13 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-23 23:23 [PATCH v2 0/9] x86/hyperv: Support wakeup mailbox for VTL2 TDX guest Yunhong Jiang
2024-08-23 23:23 ` [PATCH v2 1/9] x86/acpi: Move ACPI MADT wakeup to generic code Yunhong Jiang
2024-08-23 23:23 ` [PATCH v2 2/9] dt-bindings: x86: Add a binding for x86 wakeup mailbox Yunhong Jiang
2024-08-25 7:10 ` Krzysztof Kozlowski
2024-08-27 20:45 ` Yunhong Jiang
2024-09-10 6:13 ` Yunhong Jiang [this message]
2024-09-16 8:56 ` Krzysztof Kozlowski
2024-09-19 19:19 ` Yunhong Jiang
2024-09-19 22:15 ` Yunhong Jiang
2024-09-20 11:19 ` Krzysztof Kozlowski
2024-09-20 11:15 ` Krzysztof Kozlowski
2025-03-03 22:21 ` Ricardo Neri
2025-03-11 10:01 ` Krzysztof Kozlowski
2025-03-12 5:51 ` Ricardo Neri
2025-03-19 7:52 ` Krzysztof Kozlowski
2025-03-20 20:34 ` Ricardo Neri
2024-08-23 23:23 ` [PATCH v2 3/9] x86/dt: Support the ACPI multiprocessor wakeup for device tree Yunhong Jiang
2024-09-02 3:35 ` Michael Kelley
2024-09-03 18:35 ` Yunhong Jiang
2024-08-23 23:23 ` [PATCH v2 4/9] x86/hyperv: Parse the ACPI wakeup mailbox Yunhong Jiang
2024-09-02 3:35 ` Michael Kelley
2024-09-03 20:19 ` Yunhong Jiang
2024-09-04 14:56 ` Michael Kelley
2024-09-04 17:31 ` Yunhong Jiang
2024-08-23 23:23 ` [PATCH v2 5/9] x86/hyperv: Mark ACPI wakeup mailbox page as private Yunhong Jiang
2024-09-02 3:35 ` Michael Kelley
2024-09-02 18:38 ` Saurabh Singh Sengar
2024-09-02 20:24 ` Michael Kelley
2024-08-23 23:23 ` [PATCH v2 6/9] x86/realmode: Add memory range support to reserve_real_mode Yunhong Jiang
2024-08-23 23:23 ` [PATCH v2 7/9] x86/hyperv: Move setting the real_mode_header to hv_vtl_init_platform Yunhong Jiang
2024-08-23 23:23 ` [PATCH v2 8/9] x86/hyperv: Set realmode_limit to 4G for VTL2 TDX guest Yunhong Jiang
2024-09-02 3:35 ` Michael Kelley
2024-08-23 23:23 ` [PATCH v2 9/9] x86/hyperv: Use wakeup mailbox for VTL2 guests if available Yunhong Jiang
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=20240910061227.GA76@yjiang5-mobl.amr.corp.intel.com \
--to=yunhong.jiang@linux.intel.com \
--cc=bp@alien8.de \
--cc=conor+dt@kernel.org \
--cc=dave.hansen@linux.intel.com \
--cc=decui@microsoft.com \
--cc=devicetree@vger.kernel.org \
--cc=haiyangz@microsoft.com \
--cc=hpa@zytor.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=kys@microsoft.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rafael@kernel.org \
--cc=robh@kernel.org \
--cc=tglx@linutronix.de \
--cc=wei.liu@kernel.org \
--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