From: Juan Quintela <quintela@redhat.com>
To: KVM devel mailing list <kvm@vger.kernel.org>,
qemu-devel qemu-devel <qemu-devel@nongnu.org>
Subject: KVM call minutes for 2013-07-23
Date: Tue, 23 Jul 2013 18:29:20 +0200 [thread overview]
Message-ID: <87y58xnstb.fsf@elfo.elfo> (raw)
- Or how to confuse dates: I am very good at it (quintela)
Sorry again.
- Organizational trivia: We are changing the call number details
If you don't receive an invite in the following days, let me now.
- s390: has different reset interfaces
(only cpus, also memory, some devices)
They need to reset some specific subsystems and not others (or the
other way around, reset everything except ...)
In x86: soft reset: reset only the cpu, not the devices (keyboard
controller reset). Reset at top level resets everything. And you
can reset things a subsystem (for instance pci) with qdev. So the
infrastructure should be there.
In some platforms they need to regenerate the device tree after
reset, so there is a reset_hook() for stuff like that.
How to reset all devices except CPU?
What event should we generate for each reset type?
We can use qdev_reset() to behave as we want. What to do with non qdev devices?
Write to one register in the ppc machine.
reply other threads:[~2013-07-23 16:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87y58xnstb.fsf@elfo.elfo \
--to=quintela@redhat.com \
--cc=kvm@vger.kernel.org \
--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