From: "Andreas Färber" <afaerber@suse.de>
To: Anthony Liguori <aliguori@us.ibm.com>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: dwmw2@infradead.org, lersek@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/3] cpu: make CPU_INTERRUPT_RESET available on all targets
Date: Tue, 05 Mar 2013 17:10:59 +0100 [thread overview]
Message-ID: <51361913.2010007@suse.de> (raw)
In-Reply-To: <87zjyhsvpv.fsf@codemonkey.ws>
Am 05.03.2013 16:38, schrieb Anthony Liguori:
> Paolo Bonzini <pbonzini@redhat.com> writes:
>
>> On the x86, some devices need access to the CPU reset pin (INIT#).
>> Provide a generic service to do this, using one of the internal
>> cpu_interrupt targets. Generalize the PPC-specific code for
>> CPU_INTERRUPT_RESET to other targets, and provide a function that
>> will raise the interrupt on all CPUs.
>>
>> Since PPC does not support migration, I picked the value that is
>> used on x86, CPU_INTERRUPT_TGT_INT_1. No other arch used to use
>> CPU_INTERRUPT_TGT_INT_1.
>>
>> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
>
> This is a very nice approach.
>
> It would still be nice to remove the explicit reset registrations for
> the various cpus and instead just call cpu_soft_reset().
>
> I'm not sure "soft" is the best word. This is just a normal CPU reset
> but I won't bikeshed over that.
>
> Reviewed-by: Anthony Liguori <aliguori@us.ibm.com>
I would like to take this through qom-cpu please since I already changed
cpu_interrupt() to CPUState with my last patch series, for which the
prereqs got an Rb now.
cpu_soft_reset() still needs to live outside qom/cpu.c due to the CPU
iteration, so this would be purely mechanical.
Regards,
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2013-03-05 16:11 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-05 15:04 [Qemu-devel] [PATCH 0/3] Implement x86 soft reset Paolo Bonzini
2013-03-05 15:04 ` [Qemu-devel] [PATCH 1/3] cpu: make CPU_INTERRUPT_RESET available on all targets Paolo Bonzini
2013-03-05 15:38 ` Anthony Liguori
2013-03-05 16:10 ` Andreas Färber [this message]
2013-03-05 16:17 ` Paolo Bonzini
2013-03-05 18:00 ` Laszlo Ersek
2013-03-05 15:04 ` [Qemu-devel] [PATCH 2/3] pc: port 92 reset requires a low->high transition Paolo Bonzini
2013-03-05 17:20 ` Anthony Liguori
2013-03-05 18:05 ` Laszlo Ersek
2013-03-05 15:04 ` [Qemu-devel] [PATCH 3/3] hw: correctly implement soft reset Paolo Bonzini
2013-03-05 17:18 ` Anthony Liguori
2013-03-05 17:22 ` David Woodhouse
2013-03-05 17:43 ` Paolo Bonzini
2013-03-05 18:32 ` Laszlo Ersek
2013-03-05 15:51 ` [Qemu-devel] [PATCH 0/3] Implement x86 " David Woodhouse
2013-03-05 16:00 ` Paolo Bonzini
2013-03-05 16:13 ` Andreas Färber
2013-03-05 16:03 ` [Qemu-devel] [PATCH 4/3] wakeup: only reset the CPU Paolo Bonzini
2013-03-05 16:59 ` David Woodhouse
2013-03-05 17:10 ` Paolo Bonzini
2013-03-05 17:26 ` Peter Stuge
2013-03-05 17:42 ` Paolo Bonzini
2013-03-05 19:12 ` Laszlo Ersek
2013-03-05 19:25 ` Paolo Bonzini
2013-03-05 19:51 ` Laszlo Ersek
2013-03-06 1:45 ` Kevin O'Connor
2013-03-06 8:32 ` David Woodhouse
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=51361913.2010007@suse.de \
--to=afaerber@suse.de \
--cc=aliguori@us.ibm.com \
--cc=dwmw2@infradead.org \
--cc=lersek@redhat.com \
--cc=pbonzini@redhat.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).