From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Glauber de Oliveira Costa
<gcosta-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
Marcelo Tosatti
<mtosatti-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Subject: Re: RFC: qemu acpi hotplug
Date: Sat, 19 Jan 2008 10:14:12 +0200 [thread overview]
Message-ID: <4791B154.6060209@qumranet.com> (raw)
In-Reply-To: <478E7345.2050402-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Glauber de Oliveira Costa wrote:
> When it's more close to inclusion, I'd also post it to main qemu list.
> But right now, I'm just aiming at a first round around this draft.
>
> The attached patch is enough to make the notifications DEVICE_CHECK
> and EJECT reach the kernel. As far as I understand, some userspace
> black magic that keeps changing its scroll is needed to really put the
> processors logically off/on after the notify (acpi code itself will
> never call cpu_up/down)
>
> Just let me tell you what you think.
You aren't the only hypervisor developer to encounter this:
http://www.gossamer-threads.com/lists/linux/kernel/866461?do=post_view_threaded
The patch looks good. One thing we might change is to use just one gpe
as a "something processor related has changed" and look up some other
pio word to see exactly what, that may be simpler with larger numbers of
processors (maybe).
--
Any sufficiently difficult bug is indistinguishable from a feature.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
prev parent reply other threads:[~2008-01-19 8:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-16 21:12 RFC: qemu acpi hotplug Glauber de Oliveira Costa
[not found] ` <478E7345.2050402-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2008-01-19 8:14 ` Avi Kivity [this message]
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=4791B154.6060209@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=gcosta-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=mtosatti-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.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