From: Toshi Kani <toshi.kani@hp.com>
To: "Pandarathil, Vijaymohan R" <vijaymohan.pandarathil@hp.com>
Cc: "lenb@kernel.org" <lenb@kernel.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"joe@perches.com" <joe@perches.com>,
"bhelgaas@google.com" <bhelgaas@google.com>,
"isimatu.yasuaki@jp.fujitsu.com" <isimatu.yasuaki@jp.fujitsu.com>,
"liuj97@gmail.com" <liuj97@gmail.com>,
"srivatsa.bhat@linux.vnet.ibm.com"
<srivatsa.bhat@linux.vnet.ibm.com>,
"prarit@redhat.com" <prarit@redhat.com>,
"imammedo@redhat.com" <imammedo@redhat.com>
Subject: RE: [PATCH v2 0/4] ACPI: hotplug messages improvement
Date: Wed, 25 Jul 2012 09:31:22 -0600 [thread overview]
Message-ID: <1343230282.3010.387.camel@misato.fc.hp.com> (raw)
In-Reply-To: <EC847C0FC42FF046B94E60B168774B173164314F@G9W0337.americas.hpqcorp.net>
On Wed, 2012-07-25 at 06:15 +0000, Pandarathil, Vijaymohan R wrote:
> Hi Toshi,
>
> Tested your patches on a KVM setup. Since all your acpi_pr* macros
> are in the error path, I didn't see an easy way to trigger them.
> Instead added an acpi_pr_err() message in the success path and tested
> out vcpu addition/deletion sequence. No regressions seen in the
> functional tests and the ACPI err message comes out on the console
> and message buffer with a valid ACPI device path.
>
> Vijay
>
> Tested-by: Vijay Mohan Pandarathil<vijaymohan.pandarathil@hp.com>
Hi Vijay,
Thanks for the testing! It sounds good to me and that's how I tested as
well, i.e. copied all messages to the normal path. I will add your
Tested-by to patch 1/4 and 2/4.
-Toshi
> -----Original Message-----
> From: Kani, Toshimitsu
> Sent: Friday, July 20, 2012 9:54 AM
> To: lenb@kernel.org; linux-acpi@vger.kernel.org
> Cc: linux-kernel@vger.kernel.org; joe@perches.com; bhelgaas@google.com; isimatu.yasuaki@jp.fujitsu.com; liuj97@gmail.com; srivatsa.bhat@linux.vnet.ibm.com; prarit@redhat.com; imammedo@redhat.com; Pandarathil, Vijaymohan R; Kani, Toshimitsu
> Subject: [PATCH v2 0/4] ACPI: hotplug messages improvement
>
> This patchset improves logging messages for ACPI CPU, Memory, and
> Container hotplug notify handlers. The patchset introduces a set of
> new macro interfaces, acpi_pr_<level>(), and updates the notify
> handlers to use them. acpi_pr_<level>() appends "ACPI" prefix and
> ACPI object path to the messages. This improves diagnostics in
> hotplug operations since it identifies an object that caused an
> issue in a log file.
>
> v2:
> - Set buffer.pointer to NULL in acpi_printk().
> - Added acpi_pr_debug().
>
> ---
> This patchset applies on top of the patch below.
>
> [PATCH] ACPI: Add ACPI CPU hot-remove support
> http://marc.info/?l=linux-acpi&m=134098193327362&w=2
>
> ---
> Toshi Kani (4):
> ACPI: Add acpi_pr_<level>() interfaces
> ACPI: Update CPU hotplug messages
> ACPI: Update Memory hotplug messages
> ACPI: Update Container hotplug messages
>
> ---
> drivers/acpi/acpi_memhotplug.c | 24 ++++++++++++------------
> drivers/acpi/container.c | 6 +++---
> drivers/acpi/processor_driver.c | 36 +++++++++++++++++++++---------------
> drivers/acpi/utils.c | 34 ++++++++++++++++++++++++++++++++++
> include/acpi/acpi_bus.h | 20 ++++++++++++++++++++
> 5 files changed, 90 insertions(+), 30 deletions(-)
prev parent reply other threads:[~2012-07-25 15:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-20 16:54 [PATCH v2 0/4] ACPI: hotplug messages improvement Toshi Kani
2012-07-20 16:54 ` [PATCH v2 1/4] ACPI: Add acpi_pr_<level>() interfaces Toshi Kani
2012-07-25 7:06 ` Joe Perches
2012-07-25 17:53 ` Toshi Kani
2012-07-25 18:11 ` Joe Perches
2012-07-25 18:30 ` Toshi Kani
2012-07-20 16:54 ` [PATCH v2 2/4] ACPI: Update CPU hotplug messages Toshi Kani
2012-07-20 16:54 ` [PATCH v2 3/4] ACPI: Update Memory " Toshi Kani
2012-07-20 16:54 ` [PATCH v2 4/4] ACPI: Update Container " Toshi Kani
2012-07-25 6:15 ` [PATCH v2 0/4] ACPI: hotplug messages improvement Pandarathil, Vijaymohan R
2012-07-25 15:31 ` Toshi Kani [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=1343230282.3010.387.camel@misato.fc.hp.com \
--to=toshi.kani@hp.com \
--cc=bhelgaas@google.com \
--cc=imammedo@redhat.com \
--cc=isimatu.yasuaki@jp.fujitsu.com \
--cc=joe@perches.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuj97@gmail.com \
--cc=prarit@redhat.com \
--cc=srivatsa.bhat@linux.vnet.ibm.com \
--cc=vijaymohan.pandarathil@hp.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