From: Igor Mammedov <imammedo@redhat.com>
To: Ren Kimura <rkx1209dev@gmail.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] What should qemu do when ACPI's OST event happen.
Date: Sat, 4 Jun 2016 18:51:42 +0200 [thread overview]
Message-ID: <20160604185142.1db68d2e@nial.brq.redhat.com> (raw)
In-Reply-To: <CALoRt7RqUZdbtY7CBQqZF3nvQjY0nu8JnUjV6T4_q+nEiB05UQ@mail.gmail.com>
On Sat, 4 Jun 2016 18:05:12 +0900
Ren Kimura <rkx1209dev@gmail.com> wrote:
> When user add new DIMM to memory slot by using qemu hotplug function, under
> ACPI mode, SCI interrupt will happen and then guest OS may issue _OST event
> 0x01.
> Is it correct?
> And in such moment, what should QEMU do?
> (i.e. What does the comment "/* TODO: handle device insert OST event */" in
> acpi_memory_hotplug_write function (hw/acpi/memory_hotplug.c:119) mean? )
QEMU should do nothing with except forwarding this event to management layers
using QMP event.
>
> Thanks
> Ren
prev parent reply other threads:[~2016-06-04 16:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-04 9:05 [Qemu-devel] What should qemu do when ACPI's OST event happen Ren Kimura
2016-06-04 16:51 ` Igor Mammedov [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=20160604185142.1db68d2e@nial.brq.redhat.com \
--to=imammedo@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rkx1209dev@gmail.com \
/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).