From: Joao Martins <joao.m.martins@oracle.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Cc: linux-kernel@vger.kernel.org, Juergen Gross <jgross@suse.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Robert Moore <robert.moore@intel.com>,
linux-acpi@vger.kernel.org, xen-devel@lists.xenproject.org,
Len Brown <lenb@kernel.org>,
Erik Schmauss <erik.schmauss@intel.com>,
devel@acpica.org
Subject: Re: [Xen-devel] [PATCH v2] xen/acpi: upload _PSD info for non Dom0 CPUs too
Date: Fri, 9 Mar 2018 12:56:28 +0000 [thread overview]
Message-ID: <165abeed-3194-fe35-74f6-e2c68543c92c@oracle.com> (raw)
In-Reply-To: <4f20689f-552f-b9eb-272d-0035ba2efdd6@oracle.com>
On 03/08/2018 10:33 PM, Boris Ostrovsky wrote:
> On 03/08/2018 05:57 AM, Joao Martins wrote:
>
>> @@ -372,6 +376,15 @@ read_acpi_id(acpi_handle handle, u32 lvl, void *context, void **rv)
>>
>> pr_debug("ACPI CPU%u w/ PBLK:0x%lx\n", acpi_id, (unsigned long)pblk);
>>
>> + /* It has P-state dependencies */
>> + if (!acpi_processor_get_psd(handle, &acpi_psd[acpi_id])) {
>> + __set_bit(acpi_id, acpi_id_psd_present);
>> +
>> + pr_debug("ACPI CPU%u w/ PST:coord_type = %llu domain = %llu\n",
>> + acpi_id, acpi_psd[acpi_id].coord_type,
>> + acpi_psd[acpi_id].domain);
>> + }
>
>
> I should have noticed this earlier, but do you really need
> acpi_id_psd_present? Can you just go by acpi_psd[i] != NULL?
>
Oh yes! I was trying to be consistent with the rest of the module, but we surely
don't need that array of longs. Will respin after testing.
> Sorry for missing it in the first patch.
>
Thanks for the feedback!
> -boris
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xenproject.org
> https://lists.xenproject.org/mailman/listinfo/xen-devel
>
prev parent reply other threads:[~2018-03-09 12:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-08 10:57 Joao Martins
2018-03-08 22:33 ` [Xen-devel] " Boris Ostrovsky
2018-03-09 12:56 ` Joao Martins [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=165abeed-3194-fe35-74f6-e2c68543c92c@oracle.com \
--to=joao.m.martins@oracle.com \
--cc=boris.ostrovsky@oracle.com \
--cc=devel@acpica.org \
--cc=erik.schmauss@intel.com \
--cc=jgross@suse.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=robert.moore@intel.com \
--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®