From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: "Moore, Robert" <robert.moore@intel.com>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Cc: Ganapatrao Kulkarni <ganapatrao.kulkarni@cavium.com>,
"Zheng, Lv" <lv.zheng@intel.com>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"devel@acpica.org" <devel@acpica.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"marc.zyngier@arm.com" <marc.zyngier@arm.com>,
"catalin.marinas@arm.com" <catalin.marinas@arm.com>,
"will.deacon@arm.com" <will.deacon@arm.com>,
"hanjun.guo@linaro.org" <hanjun.guo@linaro.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"jason@lakedaemon.net" <jason@lakedaemon.net>,
"jnair@caviumnetworks.com" <jnair@caviumnetworks.com>,
"gpkulkarni@gmail.com" <gpkulkarni@gmail.com>
Subject: Re: [PATCH v4 1/2] ACPICA: ACPI 6.2: Add support for new SRAT subtable
Date: Thu, 22 Jun 2017 16:27:18 +0200 [thread overview]
Message-ID: <7426901.eKsnQBecvM@aspire.rjw.lan> (raw)
In-Reply-To: <94F2FBAB4432B54E8AACC7DFDE6C92E37E5C3067@ORSMSX110.amr.corp.intel.com>
On Thursday, June 22, 2017 02:13:18 PM Moore, Robert wrote:
> This support is already in the ACPICA code base, but I can't speak to when it will be upstreamed to Linux. Lv would know this.
It should be there in linux-next already AFAICS.
Lorenzo, can you please double check?
Thanks,
Rafael
> > -----Original Message-----
> > From: Lorenzo Pieralisi [mailto:lorenzo.pieralisi@arm.com]
> > Sent: Thursday, June 22, 2017 6:43 AM
> > To: Ganapatrao Kulkarni <ganapatrao.kulkarni@cavium.com>; Zheng, Lv
> > <lv.zheng@intel.com>; Moore, Robert <robert.moore@intel.com>; Rafael J.
> > Wysocki <rjw@rjwysocki.net>
> > Cc: linux-acpi@vger.kernel.org; devel@acpica.org; linux-
> > kernel@vger.kernel.org; linux-arm-kernel@lists.infradead.org;
> > marc.zyngier@arm.com; catalin.marinas@arm.com; will.deacon@arm.com;
> > hanjun.guo@linaro.org; tglx@linutronix.de; jason@lakedaemon.net;
> > jnair@caviumnetworks.com; gpkulkarni@gmail.com
> > Subject: Re: [PATCH v4 1/2] ACPICA: ACPI 6.2: Add support for new SRAT
> > subtable
> >
> > Hi Rafael, Lv, Robert,
> >
> > On Thu, Jun 22, 2017 at 11:40:11AM +0530, Ganapatrao Kulkarni wrote:
> > > Add GIC ITS Affinity (ACPI 6.2) subtable to SRAT table.
> > >
> > > ACPICA commit 5bc67f63918da249bfe279ee461d152bb3e6f55b
> > > Link: https://github.com/acpica/acpica/commit/5bc67f6
> > >
> > > Signed-off-by: Ganapatrao Kulkarni <ganapatrao.kulkarni@cavium.com>
> > > ---
> > > include/acpi/actbl1.h | 12 +++++++++++-
> > > 1 file changed, 11 insertions(+), 1 deletion(-)
> >
> > This patch is fine to me but it is up to you or who sends the ACPICA
> > pull request to send it upstream or give us an ACK so that it can go via
> > irqchip.
> >
> > We need to know how this commit (and other ACPICA changes) will be sent
> > upstream to handle trees dependencies, please advise it is a bit urgent,
> > thank you.
> >
> > Lorenzo
> >
> > > diff --git a/include/acpi/actbl1.h b/include/acpi/actbl1.h index
> > > b4ce55c..253c9db 100644
> > > --- a/include/acpi/actbl1.h
> > > +++ b/include/acpi/actbl1.h
> > > @@ -1192,7 +1192,8 @@ enum acpi_srat_type {
> > > ACPI_SRAT_TYPE_MEMORY_AFFINITY = 1,
> > > ACPI_SRAT_TYPE_X2APIC_CPU_AFFINITY = 2,
> > > ACPI_SRAT_TYPE_GICC_AFFINITY = 3,
> > > - ACPI_SRAT_TYPE_RESERVED = 4 /* 4 and greater are reserved */
> > > + ACPI_SRAT_TYPE_GIC_ITS_AFFINITY = 4, /* ACPI 6.2 */
> > > + ACPI_SRAT_TYPE_RESERVED = 5 /* 5 and greater are reserved */
> > > };
> > >
> > > /*
> > > @@ -1260,6 +1261,15 @@ struct acpi_srat_gicc_affinity {
> > > u32 clock_domain;
> > > };
> > >
> > > +/* 4: GIC ITS Affinity (ACPI 6.2) */
> > > +
> > > +struct acpi_srat_its_affinity {
> > > + struct acpi_subtable_header header;
> > > + u32 proximity_domain;
> > > + u16 reserved;
> > > + u32 its_id;
> > > +};
> > > +
> > > /* Flags for struct acpi_srat_gicc_affinity */
> > >
> > > #define ACPI_SRAT_GICC_ENABLED (1) /* 00: Use affinity structure
> > */
> > > --
> > > 1.8.1.4
> > >
next prev parent reply other threads:[~2017-06-22 14:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-22 6:10 [PATCH v4 0/2] acpi, gicv3-its, numa: Adding numa node mapping for ITS Ganapatrao Kulkarni
2017-06-22 6:10 ` [PATCH v4 1/2] ACPICA: ACPI 6.2: Add support for new SRAT subtable Ganapatrao Kulkarni
2017-06-22 13:43 ` Lorenzo Pieralisi
2017-06-22 14:13 ` Moore, Robert
2017-06-22 14:27 ` Rafael J. Wysocki [this message]
2017-06-22 16:21 ` Ganapatrao Kulkarni
2017-06-22 21:06 ` Lorenzo Pieralisi
2017-06-22 6:10 ` [PATCH v4 2/2] acpi, gicv3-its, numa: Adding numa node mapping for gic-its units Ganapatrao Kulkarni
2017-06-22 13:46 ` Lorenzo Pieralisi
2017-06-22 14:49 ` Marc Zyngier
2017-06-26 17:38 ` [Devel] " Robert Richter
2017-06-26 17:43 ` Marc Zyngier
2017-06-26 17:45 ` Robert Richter
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=7426901.eKsnQBecvM@aspire.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=catalin.marinas@arm.com \
--cc=devel@acpica.org \
--cc=ganapatrao.kulkarni@cavium.com \
--cc=gpkulkarni@gmail.com \
--cc=hanjun.guo@linaro.org \
--cc=jason@lakedaemon.net \
--cc=jnair@caviumnetworks.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=lv.zheng@intel.com \
--cc=marc.zyngier@arm.com \
--cc=robert.moore@intel.com \
--cc=tglx@linutronix.de \
--cc=will.deacon@arm.com \
/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