qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: Alexander Graf <agraf@suse.de>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	qemu-devel@nongnu.org, Luiz Capitulino <lcapitulino@redhat.com>,
	Christian Borntraeger <borntraeger@de.ibm.com>,
	qemu-ppc@nongnu.org, Cornelia Huck <cornelia.huck@de.ibm.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH v7 3/4] s390x: Migrate to new NMI interface
Date: Mon, 23 Jun 2014 23:32:58 +1000	[thread overview]
Message-ID: <53A82C8A.4020908@ozlabs.ru> (raw)
In-Reply-To: <539EACBC.6060705@suse.de>

On 06/16/2014 06:37 PM, Alexander Graf wrote:
> 
> On 16.06.14 10:33, Alexey Kardashevskiy wrote:
>> On 06/16/2014 05:16 PM, Cornelia Huck wrote:
>>> On Sat, 14 Jun 2014 12:41:50 +1000
>>> Alexey Kardashevskiy <aik@ozlabs.ru> wrote:
>>>
>>>> On 06/13/2014 04:00 PM, Cornelia Huck wrote:
>>>>> On Fri, 13 Jun 2014 13:36:58 +1000
>>>>> Alexey Kardashevskiy <aik@ozlabs.ru> wrote:
>>>>>
>>>>>> This implements an NMI interface for s390 and s390-ccw machines.
>>>>>>
>>>>>> This removes #ifdef s390 branch in qmp_inject_nmi so new s390's
>>>>>> nmi_monitor_handler() callback is going to be used for NMI.
>>>>>>
>>>>>> Since nmi_monitor_handler()-calling code is platform independent,
>>>>>> CPUState::cpu_index is used instead of S390CPU::env.cpu_num.
>>>>>> There should not be any change in behaviour as both @cpu_index and
>>>>>> @cpu_num are global CPU numbers.
>>>>>>
>>>>>> Also, s390_cpu_restart() takes care of preforming operations in
>>>>>> the specific CPU thread so no extra measure is required here either.
>>>>> I find this paragraph a bit confusing; I'd just remove it.
>>>> Besides bad english (please feel free to adjust it), what else is
>>>> confusing
>>>> here? I put it there because the spapr patch makes use of
>>>> async_run_on_cpu() and maintainers may ask why I do not do the same for
>>>> other platforms. This way I hoped I could reduce number of versions to
>>>> post :)
>>> What about
>>>
>>> "Note that s390_cpu_restart() already takes care of the specified cpu,
>>> so we don't need to schedule via async_run_on_cpu()."
>> I fail to see how exactly this is better or different but ok :)
>>
>>
>> Alex, should I repost it with Cornelia's suggestion? What should happen
>> next to this patchset? Who is supposed to pick it up? Thanks.
> 
> Just post v8 of that single patch with the right message-id as reference. I
> can pick up the patches, but I'd like at least an ack from Paolo on the
> whole set.


Anybody, ping? Or we are waiting till x86 machines got QOM'ed and then I'll
repost it with x86 NMI handler? Thanks!



-- 
Alexey

  reply	other threads:[~2014-06-23 13:33 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-13  3:36 [Qemu-devel] [PATCH v7 0/4] cpus: Add generic "nmi" monitor command support Alexey Kardashevskiy
2014-06-13  3:36 ` [Qemu-devel] [PATCH v7 1/4] cpus: Define callback for QEMU "nmi" command Alexey Kardashevskiy
2014-07-03  6:41   ` [Qemu-devel] [Qemu-ppc] " Nikunj A Dadhania
2014-07-03 12:36     ` Eric Blake
2014-07-15 14:50   ` [Qemu-devel] " Eric Blake
2014-07-15 15:00     ` Peter Maydell
2014-06-13  3:36 ` [Qemu-devel] [PATCH v7 2/4] s390x: Convert QEMUMachine to MachineClass Alexey Kardashevskiy
2014-06-13  3:44   ` Alexey Kardashevskiy
2014-06-13 12:47     ` Eric Blake
2014-06-13  5:56   ` Cornelia Huck
2014-06-13  3:36 ` [Qemu-devel] [PATCH v7 3/4] s390x: Migrate to new NMI interface Alexey Kardashevskiy
2014-06-13  6:00   ` Cornelia Huck
2014-06-14  2:41     ` Alexey Kardashevskiy
2014-06-16  7:16       ` Cornelia Huck
2014-06-16  8:33         ` Alexey Kardashevskiy
2014-06-16  8:37           ` Alexander Graf
2014-06-23 13:32             ` Alexey Kardashevskiy [this message]
2014-07-03  4:59               ` Alexey Kardashevskiy
2014-07-03  7:11                 ` Markus Armbruster
2014-07-14  3:17                   ` Alexey Kardashevskiy
2014-07-14 20:29                     ` Paolo Bonzini
2014-07-15  5:47                       ` Cornelia Huck
2014-07-17  6:30                       ` Alexey Kardashevskiy
2014-08-20 10:20                         ` Alexey Kardashevskiy
2014-08-20 11:20                           ` Alexander Graf
2014-08-20 11:38                             ` Alexey Kardashevskiy
2014-08-20 12:05                               ` Alexander Graf
2014-08-20 12:11                                 ` Alexey Kardashevskiy
2014-08-20 12:12                                   ` Alexander Graf
2014-08-20 13:13                                     ` Paolo Bonzini
2014-06-13  3:36 ` [Qemu-devel] [PATCH v7 4/4] spapr: Add support for " Alexey Kardashevskiy
2014-06-13 10:50 ` [Qemu-devel] [PATCH v7 0/4] cpus: Add generic "nmi" monitor command support Alexander Graf
2014-06-16  8:57 ` [Qemu-devel] [PATCH v8] s390x: Migrate to new NMI interface Alexey Kardashevskiy
2014-06-16 10:56   ` Cornelia Huck

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=53A82C8A.4020908@ozlabs.ru \
    --to=aik@ozlabs.ru \
    --cc=agraf@suse.de \
    --cc=borntraeger@de.ibm.com \
    --cc=cornelia.huck@de.ibm.com \
    --cc=lcapitulino@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=rth@twiddle.net \
    /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).