From: "Jason J. Herne" <jjherne@linux.vnet.ibm.com>
To: "Andreas Färber" <afaerber@suse.de>,
"Jason J. Herne" <jjherne@us.ibm.com>,
borntraeger@de.ibm.com
Cc: agraf@suse.de, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/4] s390-cpu: ipi_states enhancements
Date: Thu, 06 Mar 2014 09:54:10 -0500 [thread overview]
Message-ID: <53188C12.5010605@linux.vnet.ibm.com> (raw)
In-Reply-To: <5310B993.6080809@suse.de>
On 02/28/2014 11:30 AM, Andreas Färber wrote:
> Am 26.02.2014 18:18, schrieb Jason J. Herne:
>> From: "Jason J. Herne" <jjherne@us.ibm.com>
>>
>> Modify s390_cpu_addr2state to allow fetching state information for cpu addresses
>> above smp_cpus. Hotplug requires this capability.
>>
>> Also add s390_cpu_set_state function to allow modification of ipi_state entries
>> during hotplug.
>>
>> Signed-off-by: Jason J. Herne <jjherne@us.ibm.com>
>
> This patch is *still* present despite your previous response that you
> incorporated my review comments. You are adding a custom s390x API here
> rather than reusing the generic QOM API as requested. I don't even read
> further in such cases - like I pointed out, a pure resend is not helping
> address review feedback!
>
> Andreas
>
Andreas,
My apologies, I am not trying to ruffle any feathers and I certainly
have not intended to make you feel like I've ignored your review
comments. I believe, if you look at patches 3 and 4 you will find that
I've address the majority of your comments. I've even completed the work
that adds the link property as you have suggested.
The reason the ipi_array still exists in my patch set is because I was
under the impression that we needed it to still exist. This belief
stemmed from a misunderstanding I had related to an earlier e-mail
discussion. I apologize for getting that detail wrong. I had assumed we
would make use of the link property when possible but still keep the
array around too.
At this point, I only have one concern about removing the array.
ipi_states is accessed from some high frequency code paths dealing with
interrupt handling. I have not yet looked into it myself, but I trust I
would find that retrieving the link property value would not
significantly affect performance?
Thank you for taking the time to read this patch set. Please let me know
if you have any more concerns. I'm happy to work with you to address them.
P.S. Sorry for taking so long to respond, I was away on vacation for a
few days and I was not checking mail.
--
-- Jason J. Herne (jjherne@linux.vnet.ibm.com)
next prev parent reply other threads:[~2014-03-06 14:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-26 17:18 [Qemu-devel] [PATCH 0/4] s390 cpu-hotplug implementation Jason J. Herne
2014-02-26 17:18 ` [Qemu-devel] [PATCH 1/4] s390: Storage key global access Jason J. Herne
2014-02-26 17:18 ` [Qemu-devel] [PATCH 2/4] s390-cpu: ipi_states enhancements Jason J. Herne
2014-02-28 16:30 ` Andreas Färber
2014-03-06 14:54 ` Jason J. Herne [this message]
2014-03-06 16:23 ` Jason J. Herne
2014-02-26 17:18 ` [Qemu-devel] [PATCH 3/4] s390-cpu: s390 cpu init improvements for hotplug Jason J. Herne
2014-02-26 17:18 ` [Qemu-devel] [PATCH 4/4] s390-hotplug: Implement hot_add_cpu hook Jason J. Herne
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=53188C12.5010605@linux.vnet.ibm.com \
--to=jjherne@linux.vnet.ibm.com \
--cc=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=borntraeger@de.ibm.com \
--cc=jjherne@us.ibm.com \
--cc=qemu-devel@nongnu.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).