qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Christian Borntraeger <borntraeger@de.ibm.com>
To: "Andreas Färber" <afaerber@suse.de>,
	jjherne@linux.vnet.ibm.com, "Jason J. Herne" <jjherne@us.ibm.com>
Cc: agraf@suse.de, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] s390: Storage key global access
Date: Tue, 25 Feb 2014 22:17:23 +0100	[thread overview]
Message-ID: <530D0863.2070409@de.ibm.com> (raw)
In-Reply-To: <530CF063.3020505@suse.de>

On 25/02/14 20:34, Andreas Färber wrote:
> Hi,
> 
> Am 25.02.2014 20:15, schrieb Christian Borntraeger:
>> On 25/02/14 15:34, Jason J. Herne wrote:
>>
>>> Christian, at one point you mentioned that it might be helpful to see this patch in the context of the rest of the hotplug patches. If you still feel this way let me know and I'll post the 4-patch series. If not, I still propose this one for s390-next. Thanks :).
>>
>> Do you feel your series is ready for upstream, then yet please post the whole series. 
>> Posting independent things is good, but I feel that the storage key rework makes more
>> sense if the followup patches make clear why.
> 
> I had requested changes to that series that apparently I could not
> communicate in a form Jason could digest, and I have since been caught
> in downstream work and a backlog of other patches, not getting to
> writing the alternative myself yet nor will I the next few days.

I think posting the full series is the right thing to do. We already merged
the sclp related changes, so the leftover patch(es) should be pretty small.
Maybe the current state is already pretty close to what you want.

> 
> An outline of the idea as far as I remember was dropping the ipi array
> instead of refactoring it to dynamic allocation and - having discussed
> that a topology will not be needed - add them as cpu[n] child<s390-cpu>
> properties of /machine, allowing access via QOM property getters instead
> of some self-cooked solution. Open question was link<> or child<>
> property and, if link<>, whether some setter hook in QOM infrastructure
> may be needed to trigger the hot-add or whether QOM realize event will
> be sufficient.
> 
> I'd still be interested in getting vCPU hotplug for s390x in 2.0, so
> maybe you can re-read my previous comments with a view to making -device
> and cpu-add work with minimum workarounds on your own? We still don't
> have model subclasses BTW, do we?
> 
> Regards,
> Andreas
> 

  reply	other threads:[~2014-02-25 21:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-22 15:48 [Qemu-devel] [PATCH] s390: Storage key global access Jason J. Herne
2014-02-03 20:09 ` Jason J. Herne
2014-02-06 15:19 ` Christian Borntraeger
2014-02-25 14:34   ` Jason J. Herne
2014-02-25 19:15     ` Christian Borntraeger
2014-02-25 19:34       ` Andreas Färber
2014-02-25 21:17         ` Christian Borntraeger [this message]
2014-02-26 14:57         ` 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=530D0863.2070409@de.ibm.com \
    --to=borntraeger@de.ibm.com \
    --cc=afaerber@suse.de \
    --cc=agraf@suse.de \
    --cc=jjherne@linux.vnet.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).